Smartpad smartdock

ABSTRACT

A multi-display device is adapted to be dockable or otherwise associatable with an additional device. In accordance with one exemplary embodiment, the multi-display device is dockable with a smartpad. The exemplary smartpad can include a screen, a touch sensitive display, a configurable area, a gesture capture region(s) and a camera. The smartpad can also include a port adapted to receive the device. The exemplary smartpad is able to cooperate with the device such that information displayable on the device is also displayable on the smartpad. Furthermore, any one or more of the functions on the device are extendable to the smartpad, with the smartpad capable of acting as an input/output interface or extension of the smartpad. Therefore, for example, information from one or more of the displays on the multi-screen device is displayable on the smartpad.

CROSS REFERENCE TO RELATED APPLICATION

The present application claims the benefits of and priority, under 35U.S.C. §119(e), to U.S. Provisional Application Ser. No. 61/539,884,filed Sep. 27, 2011, entitled “MOBILE DEVICE,” and is related to: Ser.No. 13/408,828, entitled “Smartpad Screen Management,” Ser. No.13/408,839, entitled “Smartpad Screen Modes,” Ser. No. 13/364,152,entitled “Desktop Application Manager: Card Dragging of Dual ScreenCards—Smartpad,” Ser. No. 13/299,279, entitled “Email Client DisplayTransitions Between Portrait and Landscape in a Smartpad Device,” andSer. No. 13/299,284, entitled “Email Client Mode Transitions in aSmartpad Device.” Each of the aforementioned documents is incorporatedherein by reference in their entirety for all that they teach and forall purposes.

BACKGROUND

A substantial number of handheld computing devices, such as cellularphones, tablets, and E-Readers, make use of a touch screen display notonly to deliver display information to the user but also to receiveinputs from user interface commands. While touch screen displays mayincrease the configurability of the handheld device and provide a widevariety of user interface options, this flexibility typically comes at aprice. The dual use of the touch screen to provide content and receiveuser commands, while flexible for the user, may obfuscate the displayand cause visual clutter, thereby leading to user frustration and lossof productivity.

The small form factor of handheld computing devices requires a carefulbalancing between the displayed graphics and the area provided forreceiving inputs. On the one hand, the small display constrains thedisplay space, which may increase the difficulty of interpreting actionsor results. On the other, a virtual keypad or other user interfacescheme is superimposed on or positioned adjacent to an executingapplication, requiring the application to be squeezed into an evensmaller portion of the display.

This balancing act is particularly difficult for single display touchscreen devices. Single display touch screen devices are crippled bytheir limited screen space. When users are entering information into thedevice, through the single display, the ability to interpret informationin the display can be severely hampered, particularly when a complexinteraction between display and interface is required.

SUMMARY

There is a need for a dual multi-display handheld computing device thatprovides for enhanced power and/or versatility compared to conventionalsingle display handheld computing devices. These and other needs areaddressed by the various aspects, embodiments, and/or configurations ofthe present disclosure. Also, while the disclosure is presented in termsof exemplary embodiments, it should be appreciated that individualaspects of the disclosure can be separately claimed.

Additionally, it is desirable to have the multi-display device bedockable or otherwise associatable with an additional device. Inaccordance with one exemplary embodiment, the multi-display device isdockable with a smartpad. The exemplary smartpad can include a screen, atouch sensitive display, a configurable area, a gesture captureregion(s) and a camera. The smartpad can also include a port adapted toreceive the device. The exemplary smartpad is able to cooperate with thedevice such that information displayable on the device is alsodisplayable on the smartpad. Furthermore, any one or more of thefunctions on the device are extendable to the smartpad, with thesmartpad capable of acting as an input/output interface or extension ofthe smartpad. Therefore, for example, information from one or more ofthe displays on the multi-screen device is displayable on the smartpad.

The present disclosure can provide a number of advantages depending onthe particular aspect, embodiment, and/or configuration.

For example, the smartpad could provide additional display area toassist a user with viewing content on the device.

Additionally, power sharing and management functions are available dueto, for example, the larger size of the smartpad that could be used forpower storage.

Furthermore, the smartpad allows functions of a communications device tobe extended to a tablet-like platform and/or form factor.

Even further, the disclosure provides techniques directed towardtranslating or otherwise converting content for a multi-display deviceinto content for a single screen device.

Moreover, the smartpad provides additional input areas adapted toreceive input beyond that of the touchscreen.

Additional advantages are directed toward managing the display of one ormore windows associated with one or more applications on a multi-displaydevice on a single display device.

Further advantages are directed toward emulation of multi-screen contenton a single screen device.

Exemplary aspects are also directed toward:

1. A smartpad comprising:

a display;

an interface adapted to receive a dual screen device, wherein contentfrom the dual screen device is displayable on the display; and

a capacitive button that toggles between one or more application modeson the smartpad.

2. The smartpad of aspect 1, further comprising a gesture captureregion.

3. The smartpad of aspect 1, further comprising one or more of aheadphone jack, a power button, at least one camera, a power connectorand one or more configurable areas.

4. The smartpad of aspect 1, further comprising one or more of a wiredand wireless communications link between the dual screen device and thesmartpad.

5. The smartpad of aspect 1, further comprising a window managementmodule adapted to transition information displayed on the dual screendevice to the display on the smartpad.

6. The smartpad of aspect 1, wherein the dual screen device docks to areceiving port in the smartpad.

7. The smartpad of aspect 1, further comprising one or more of a line injack, a line out jack, a microphone jack and a communication port.

8. The smartpad of aspect 1, wherein the display is capable of renderingthe content displayed on each of the screens on the dual screen deviceupon docking of the dual screen device to the smartpad.

9. The smartpad of aspect 1, further comprising:

a link between the smartpad and the dual screen device allowing theexchange of power; and

a link between the smartpad and a dock adapted for charging thesmartpad, wherein the dock can further be used to charge the dual screendevice, the dock including one or more of a headphone jack, a line jack,a USB connector, an AC port and a display port, all connectable to oneor more of the smartpad and the dual screen device.

10. The smartpad of aspect 1, wherein the display is a touch sensitivedisplay.

11. A method for operating a smartpad comprising:

receiving a dual screen device in an interface, wherein content from thedual screen device is displayable on a display of the smartpad upon adocking event being detected; and

toggling between one or more application modes on the smartpad based oninput received from a capacitive button.

12. The method of aspect 11, further comprising detecting one or moregestures in a gesture capture region.

13. The method of aspect 11, wherein the smartpad includes one or moreof a headphone jack, a power button, at least one camera, a powerconnector and one or more configurable areas.

14. The method of aspect 11, wherein the smartpad includes one or moreof a wired and wireless communications link between the dual screendevice and the smartpad.

15. The method of aspect 11, further comprising transitioninginformation displayed on the dual screen device to the display on thesmartpad.

16. The method of aspect 11, wherein the dual screen device docks to areceiving port in the smartpad.

17. The method of aspect 11, wherein the smartpad includes one or moreof a line in jack, a line out jack, a microphone jack and acommunication port.

18. The method of aspect 1, wherein the display is capable of renderingthe content displayed on each of the screens on the dual screen deviceupon docking of the dual screen device to the smartpad.

19. The method of aspect 11, further comprising exchanging power on alink between the smartpad and the dual screen device.

20. The s method of aspect 11, wherein the display is a touch sensitivedisplay.

Further exemplary aspects are directed toward:

1. A smartpad comprising:

a screen; and

a display, the display configured to display content from a dockedmulti-screen device, the content including one or more of a first windowcorresponding to a first application and a second window correspondingto second application, wherein both windows are capable of beingoriented and displayed on the display based on a detected orientation ofthe smartpad.

2. The smartpad of aspect 1, wherein the display is a touch screendisplay.

3. The smartpad of aspect 1, wherein the smartpad has a portrait modeand a landscape mode.

4. The smartpad of aspect 1, wherein one or more of:

an application in focus remains in focus on the smartpad,

the display is capable of being logically divided into at least twoportions,

the first application is a dual screen application, and

a virtual keyboard is displayed in a landscape mode or a portrait mode.

5. The smartpad of aspect 4, wherein a first of the logical portionsdisplays the first window from the multi-screen device and a second ofthe logical portions displays the second window from the multi-screendevice.

6. The smartpad of aspect 5, wherein the at least two portions aredifferent sizes and relate to two different applications.

7. The smartpad of aspect 1, wherein the smartpad further supports amulti-application mode, the multi-application mode emulating the dockedmulti-screen device in mini-tablet form.

8. A method comprising:

displaying content from a docked multi-screen device, the contentincluding one or more of a first window corresponding to a firstapplication and a second window corresponding to second application,wherein both windows are capable of being oriented and displayed on thedisplay based on a detected orientation of a smartpad.

9. The method of aspect 8, wherein the display is a touch screendisplay.

10. The method of aspect 8, wherein the smartpad has a portrait mode anda landscape mode.

11. The method of aspect 8, wherein one or more of:

an application in focus remains in focus on the smartpad,

the display is capable of being logically divided into at least twoportions,

the first application is a dual screen application, and

a virtual keyboard is displayed in landscape mode or a portrait mode.

12. The method of aspect 11, wherein a first of the logical portionsdisplays the first window from the multi-screen device and a second ofthe logical portions displays the second window from the multi-screendevice.

13. The method of aspect 12, wherein the at least two portions aredifferent sizes and relate to two different applications.

14. The method of aspect 8, wherein both windows occupy all orsubstantially all of the display.

15. The method of aspect 8, further comprising resizing one or more ofthe windows.

16. The method of aspect 8, further comprising redrawing one or more ofthe windows.

17. The method of aspect 8, further comprising determining anorientation of the smartpad and aligning an orientation of one or moreof the windows with the orientation of the smartpad.

18. The method of aspect 8, wherein the smartpad further supports amulti-application mode, the multi-application mode emulating the dockedmulti-screen device in mini-tablet form.

19. The method of aspect 8, further comprising receiving a request toenter multi-application mode, and, in response thereto, splitting thedisplay into at least two logical portions, a first portion fordisplaying the first window and a second portion for displaying thesecond window.

20. The method of aspect 8, further comprising detecting the pressing ofa power button and performing one of the following:

waking the smartpad,

toggling a standby mode,

performing a hard reset,

powering on the smartpad,

powering off the smartpad,

displaying an on screen display, and

displaying a smartpad power menu.

Even further exemplary aspects are directed toward:

1. A smartpad comprising:

a screen; and

a display, the display configured to display content from a dockedmulti-screen device, the content including a virtual keyboard, whereinat least one application from the docked multi-screen device isdisplayed in conjunction with the virtual keyboard on the display.

2. The smartpad of aspect 1, wherein the display further displays one ormore keys associated with a slider bar.

3. The smartpad of aspect 1, wherein the smartpad has a portrait modeand a landscape mode.

4. The smartpad of aspect 1, wherein one or more of:

the display is capable of being logically divided into at least twoportions,

the application is a dual screen application, and

the virtual keyboard has a landscape mode and a portrait mode.

5. The smartpad of aspect 6, wherein a first of the logical portionsdisplays a first window from the multi-screen device and a second of thelogical portions displays a second window from the multi-screen device.

6. The smartpad of aspect 5, wherein the at least two portions aredifferent sizes and relate to two different applications.

7. The smartpad of aspect 1, wherein the virtual keyboard is dynamicallypopulated with keys based on an application in focus.

8. A method comprising:

displaying content from a docked multi-screen device on a display of asmartpad, the content including at least one virtual keyboard, whereinat least one application on the docked multi-screen device is displayedwith the virtual keyboard on the display.

9. The method of aspect 8, wherein the virtual keyboard is dynamicallypopulated with keys based on an application in focus.

10. The method of aspect 8, wherein the display further displays one ormore keys associated with a slider bar.

11. The method of aspect 8, wherein one or more of:

the display is capable of being logically divided into at least twoportions,

the application is a dual screen application, and

the virtual keyboard has a landscape mode and a portrait mode.

12. The method of aspect 11, wherein a first of the logical portionsdisplays a first window from the multi-screen device and a second of thelogical portions displays a second window from the multi-screen device.

13. The method of aspect 12, wherein the at least two portions aredifferent sizes and relate to two different applications.

14. The method of aspect 8, wherein the keyboard can have a portrait orlandscape orientation.

15. The method of aspect 8, further comprising resizing the application.

16. The method of aspect 8, further comprising redrawing theapplication.

17. The method of aspect 8, further comprising determining anorientation of the smartpad and aligning an orientation of theapplication with an orientation of the smartpad.

18. The method of aspect 8, wherein the smartpad further supports amulti-application mode, the multi-application mode emulating the dockedmulti-screen device in mini-tablet form.

19. The method of aspect 8, further comprising receiving a gesturerequesting viewing of a new application, and, in response thereto,scrolling though one or more available windows corresponding toavailable applications.

20. The method of aspect 8, wherein the virtual keyboard and slider barare dynamically populated with keys based on an application in focus.

Additional exemplary aspects are also directed toward:

1. A smartpad comprising:

a screen; and

a display, the display configured to display content from a dockedmulti-screen device, the content including a contextual keyboard,wherein at least one application from the docked multi-screen device isdisplayed in conjunction with the contextual keyboard on the display.

2. The smartpad of aspect 1, wherein the display further displays one ormore keys associated with a slider bar.

3. The smartpad of aspect 1, wherein the contextual keyboard is chosenbased on an application in focus.

4. The smartpad of aspect 1, wherein the contextual keyboard is one:

a standard keyboard;

an uppercase keyboard;

a punctuation/number keyboard;

a secondary/alternative punctuation keyboard;

a messaging keyboard;

an email keyboard;

an internet keyboard; and

a number layout.

5. The smartpad of aspect 6, wherein a first of the logical portionsdisplays a first window from the multi-screen device and a second of thelogical portions displays a second window from the multi-screen device.

6. The smartpad of aspect 5, wherein the at least two portions aredifferent sizes and relate to two different applications.

7. The smartpad of aspect 1, wherein the contextual keyboard isdynamically populated with keys based on an application in focus.

8. A method comprising:

displaying content from a docked multi-screen device on a display of asmartpad, the content including at least one contextual keyboard,wherein at least one application on the docked multi-screen device isdisplayed with the contextual keyboard on the display.

9. The method of aspect 8, wherein the contextual keyboard isdynamically populated with keys based on an application in focus.

10. The method of aspect 8, wherein the display further displays one ormore keys associated with a slider bar.

11. The method of aspect 8, wherein one or more of:

a standard keyboard;

an uppercase keyboard;

a punctuation/number keyboard;

a secondary/alternative punctuation keyboard;

a messaging keyboard;

an email keyboard;

an internet keyboard; and

a number layout.

12. The method of aspect 11, wherein a first of the logical portionsdisplays a first window from the multi-screen device and a second of thelogical portions displays a second window from the multi-screen device.

13. The method of aspect 12, wherein the at least two portions aredifferent sizes and relate to two different applications.

14. The method of aspect 8, wherein the keyboard can have a portrait orlandscape orientation.

15. The method of aspect 8, further comprising resizing the application.

16. The method of aspect 8, further comprising redrawing theapplication.

17. The method of aspect 8, further comprising determining anorientation of the smartpad and aligning an orientation of theapplication with an orientation of the smartpad.

18. The method of aspect 8, wherein the smartpad further supports amulti-application mode, the multi-application mode emulating the dockedmulti-screen device in mini-tablet form.

19. The method of aspect 8, further comprising receiving a gesturerequesting viewing of a new application, and, in response thereto,scrolling though one or more available windows corresponding toavailable applications.

20. The method of aspect 8, wherein the contextual keyboard and a sliderbar are automatically chosen based on an application in focus.

More exemplary aspects are directed toward:

1. A smartpad comprising:

a screen; and

a display, the display configured to display content from a multi-screendevice upon a docking event occurring, the content displayed on thedisplay based on an orientation of the smartpad, an application mode ofthe smartpad and focus of an application on the multi-screen device.

2. The smartpad of aspect 1, wherein the multi-screen device is in alandscape or a portrait orientation and the smartpad is in a landscapeor portrait orientation.

3. The smartpad of aspect 1, wherein the smartpad is in a singleapplication mode or a dual application mode.

4. The smartpad of aspect 1, wherein the multi-screen device is in asingle application mode or a dual application mode.

5. The smartpad of aspect 1, wherein a last state of the smartpad isstored and recalled for a re-docking event.

6. The smartpad of aspect 1, wherein an application is displayed in amax mode.

7. The smartpad of aspect 1, wherein an application in an applicationstack is represent by a screenshot.

8. The smartpad of aspect 7, wherein the screenshot is one or more ofresized and re-oriented based on the orientation.

9. The smartpad of aspect 7, wherein the screenshot is presented in adimmed view.

10. The smartpad of aspect 7, wherein the screenshot, upon beingcompletely revealed, triggers the activation of a correspondingapplication.

11. A method to operate a smartpad comprising:

displaying content from a multi-screen device on a display of thesmartpad upon a docking event occurring, the content displayed on thedisplay based on an orientation of the smartpad, an application mode ofthe smartpad and focus of an application on the multi-screen device.

12. The method of aspect 11, wherein the multi-screen device is in alandscape or a portrait orientation and the smartpad is in a landscapeor portrait orientation.

13. The method of aspect 11, wherein the smartpad is in a singleapplication mode or a dual application mode.

14. The method of aspect 11, wherein the multi-screen device is in asingle application mode or a dual application mode.

15. The method of aspect 11, wherein a last state of the smartpad isstored and recalled for a re-docking event.

16. The method of aspect 11, wherein an application is displayed in amax mode.

17. The method of aspect 11, wherein an application in an applicationstack is represent by a screenshot.

18. The method of aspect 17, wherein the screenshot is one or more ofresized and re-oriented based on the orientation.

19. The method of aspect 17, wherein the screenshot is presented in adimmed view.

20. The method of aspect 17, wherein the screenshot, upon beingcompletely revealed, triggers the activation of a correspondingapplication.

Even more exemplary aspects are directed toward:

1. A smartpad comprising:

a screen; and

a display, the display configured to display content from a multi-screendevice upon a docking event occurring, the smartpad emulating themulti-screen device in an opened state upon selection of amulti-application mode button.

2. The smartpad of aspect 1, wherein a multi-application mode displaystwo applications on the display simultaneously, with one of the twoapplications having a corresponding focus indicator.

3. The smartpad of aspect 2, wherein the focus indicator is one or moreof a bar, a highlight, a border, a change in location on the displayrelative to the other application, a change in color relative to theother application and a change in brightness relative to the otherapplication.

4. The smartpad of aspect 1, wherein an application can be expanded to adual screen mode or a max mode.

5. The smartpad of aspect 2, wherein one of the applications is adesktop.

6. The smartpad of aspect 2, wherein one of the applications is akeyboard.

7. The smartpad of aspect 1, wherein a desktop is displayed after a lastapplication in a stack has been displayed.

8. The smartpad of aspect 1, wherein back, menu and home buttons areprovided.

9. The smartpad of aspect 1, wherein multiple sets of back, menu andhome buttons are provided.

10. The smartpad of aspect 1, wherein the emulation is an emulation of amini-tablet mode.

11. A method for operating a smartpad comprising:

displaying content from a multi-screen device on a display of thesmartpad upon a docking event occurring, the smartpad emulating themulti-screen device in an opened state upon selection of amulti-application mode button.

12. The method of aspect 11, wherein a multi-application mode displaystwo applications on the display simultaneously, with one of the twoapplications having a corresponding focus indicator.

13. The method of aspect 12, wherein the focus indicator is one or moreof a bar, a highlight, a border, a change in location on the displayrelative to the other application, a change in color relative to theother application and a change in brightness relative to the otherapplication.

14. The method of aspect 11, wherein an application can be expanded to adual screen mode or a max mode.

15. The method of aspect 12, wherein one of the applications is adesktop.

16. The method of aspect 12, wherein one of the applications is akeyboard.

17. The method of aspect 11, wherein a desktop is displayed after a lastapplication in a stack has been displayed.

18. The method of aspect 11, wherein back, menu and home buttons areprovided.

19. The method of aspect 11, wherein multiple sets of back, menu andhome buttons are provided.

20. The method of aspect 11, wherein the emulation is an emulation of amini-tablet mode.

Exemplary aspects are also directed toward:

1. A method for controlling a display of a window on a smartpad, thesmartpad displaying content from a multi-screen device on a singledisplay comprising:

providing a windows stack, wherein at least a first window in thewindows stack is in an active and displayed state on the single display,wherein at least a second window in the windows stack is in an inactiveand not displayed state, and wherein the second window is stored inmemory as one of an image of the second window as it appeared in one ofa last active state or an image representing the second window;

presenting using on the single display the first window in the activeand displayed of state;

receiving a first user input, wherein the first user input includes asignal to uncover the second window and cover the first window;

discontinuing the presentation of the first window;

presenting on the single display the second window, wherein the secondwindow is presented in an inactive state and displayed state.

2. The method of aspect 1, wherein while displayed in the inactivestate, the second window is displayed as it appeared in a last activestate or an image representing the second window.

3. The method of aspect 2, further comprising:

putting the first window in an inactive and not displayed state, whereinthe first window is stored in memory as one of an image of the firstwindow as it appeared in one of a last active state when the user inputincluding a signal to uncover the second window and cover the firstwindow was received or an image representing the first window.

4. The method of aspect 3, further comprising:

initiating operation of a timer at a time corresponding to thepresenting the second window.

5. The method of aspect 4, further comprising:

at an expiration of a predetermined time, as determined by the timer,placing the second window in an active and displayed state.

6. The method of aspect 5, wherein prior to the expiration of thepredetermined time, the second window remains in the inactive anddisplayed state.

7. The method of aspect 3, wherein a third window in the windows stackis in an inactive and not displayed state, and wherein the third windowis stored in memory as one of an image of the third window as itappeared in one of a last active state or an image representing thethird window, the method further comprising:

receiving a second user input, wherein the second user input includes asignal to uncover the third window and cover the second window;

discontinuing the presentation of the second window;

presenting using the at least a first screen the third window, whereinthe third window is presented in an inactive and displayed state.

8. The method of aspect 7, wherein during the presentation of the secondwindow between at least the receipt of the first user input and thereceipt of the second user input the second window remains in theinactive state and displayed state.

9. The method of aspect 1, wherein a third window in the windows stackis in an active and displayed state, the method further comprising:

presenting the third window in the active and displayed state.

10. The method of aspect 9, wherein the third window remains in theactive and displayed state during the discontinuation of thepresentation of the first window and the presentation of the secondwindow.

11. A smartpad, comprising:

a first screen, wherein the first screen includes a first touchsensitive display;

memory;

a processor in communication with the first screen and the memory;

a dock adapted to receive a multi-screen device; and

application programming stored in the memory and executed by theprocessor, wherein the application programming is operable to:

maintain at least a first set of windows, wherein the at least a firstset of windows is stored in the memory, wherein the first set of windowsincludes a plurality of windows, wherein at least a first window in thefirst set of windows is in one of an active and displayed state or aninactive and displayed state, wherein at least a second window in thefirst set of windows is in an inactive and not displayed state, andwherein the second window is stored in memory as one of an image of thesecond window as it appeared in one of a last active state or an imagerepresenting the second window;

present the first window in the one of the active and displayed state orthe inactive and displayed state using the first screen;

receive a first user input, wherein the first user input includes asignal to present the second window and discontinue the presentation ofthe first window;

in response to the first user input, discontinue the presentation of thefirst window and present the second window in an inactive and displayedstate using the first screen.

12. The device of aspect 11, wherein the second window is presented inthe form of the image stored in memory for at least a first period oftime.

13. The device of aspect 11, wherein the application programming isfurther operable to continue to implement a timer, wherein after theexpiration of the first period of time the second window is activatedand is presented in an active and displayed state.

14. The device of aspect 12, wherein the plurality of windows in thefirst set of windows includes a third window, wherein the applicationprogramming is further operable to:

receive a second user input, wherein the second user input includes asignal to present the third window and discontinue the presentation ofthe second window, wherein the second user input is received while thesecond window is presented in the inactive and displayed state;

in response to the second user input, discontinue the presentation ofthe second window and present the second window in an inactive anddisplayed state.

15. The device of aspect 11, wherein the application programming isfurther operable to maintain a second set of windows, wherein the secondset of windows is stored in memory, wherein the second set of windowsincludes a third window, wherein the third window is in an active anddisplayed state, and wherein the third window is presented in the activeand displayed state for at least a portion of a time that the firstwindow is displayed by the first screen and for at least a portion of atime that the second window is displayed by the first screen.

16. A non-transitory computer readable medium having stored thereoncomputer-executable instructions, the computer executable instructionscausing a processor to execute a method for controlling a user interfaceof a device, the computer-executable instructions comprising:

instructions to emulate the display of a multi-screen device on a singlescreen device upon completion of a docking event;

instructions to maintain a first set of windows, wherein at least afirst window is maintained in the first set of windows as an active anddisplayed window, and wherein at least a second window is maintained inthe first set of windows as an inactive and not displayed window;

instructions to present the first window on a first screen of the devicein the active and displayed state;

instructions to receive a first user interface event, wherein the firstuser interface event directs the second window to be placed in adisplayed state; and

instructions to, in response to the first user interface event directingthe second window to be placed in a displayed state, place the firstwindow in an inactive and not displayed state and to present the secondwindow on the first screen of the device in an inactive and displayedstate.

17. The computer readable medium of aspect 16, wherein in the inactiveand displayed state the second window is presented as an image of thewindow in a last active state.

18. The computer readable medium of aspect 16, the computer executableinstructions further comprising:

instructions to maintain a second set of windows, wherein at least athird window is maintained in the second set of windows as an active anddisplayed window, and wherein at least a fourth window is maintained inthe second set of windows as an inactive and not displayed window;

instructions to present the third window on a second screen of thedevice in an active and displayed state;

instructions to receive a second user interface event, wherein thesecond user interface event directs the fourth window to be placed in adisplayed state;

instructions to, in response to the second user interface eventdirecting the fourth window to be placed in a displayed state, place thethird window in an inactive and not displayed state and to present thefourth window on the second screen of the device in an inactive anddisplayed state.

19. The computer readable medium of aspect 18, wherein for at least afirst period of time the second window is presented on the first screenof the device in the inactive and displayed state and the fourth windowis presented on a second portion of the first screen of the device inthe inactive and displayed state.

20. The computer readable medium of aspect 19, wherein first userinterface event is received before the second user interface event, andwherein after the first period of time and for at least a second periodof time the second window is presented in an active and displayed stateand the fourth window is displayed in the inactive and displayed state.

Exemplary aspects are further directed toward:

1. A smartpad comprising:

a display;

an interface adapted to receive a dual screen device, wherein contentfrom the dual screen device is displayable on the display; and

a visual seam is provided between two applications when displayed on thedisplay, the seam representing a physical seam that is present on thedual screen device.

2. The smartpad of aspect 1, wherein the seam further provides anindication of focus for an in focus application of the two applications.

3. The smartpad of aspect 1, wherein one of the two applications is adesktop.

4. The smartpad of aspect 1, wherein the smartpad is in a landscape orportrait orientation.

5. The smartpad of aspect 1, wherein toggling between a single and adual application mode toggles which of the two applications is shown,wherein in the single application mode, one application is shown on thefull display.

6. The smartpad of aspect 1, wherein toggling between a single and adual application mode toggles which of the two applications is shown,wherein in the dual application mode, the two applications are shown onthe full display with the seam.

7. The smartpad of aspect 6, wherein an indication is provided to theuser indicating whether the smartpad is in the single or the dualapplication mode.

8. The smartpad of aspect 1, wherein upon receipt of an incoming call onthe smartpad in dual application mode, an incoming call application islaunched on a primary portion of the display.

9. The smartpad of aspect 1, wherein upon receipt of an incoming call onthe smartpad in single application mode, an incoming call application islaunched on a primary portion of the display after the smartpad switchesto dual application mode.

10. The smartpad of aspect 1, wherein upon receipt of an incoming callon the smartpad in single application mode, an incoming call applicationis launched on a primary portion of the display after the smartpadswitches to dual application mode and the seam is placed between theprimary portion and a secondary portion showing a minimized secondapplication.

11. A method for operating a smartpad comprising:

providing a visual seam between two applications when displayed on adisplay of the smartpad, the seam representing a physical seam that ispresent on a dual screen device docked with the smartpad.

12. The method of aspect 11, wherein the seam further provides anindication of focus for an in focus application of the two applications.

13. The method of aspect 11, wherein one of the two applications is adesktop.

14. The method of aspect 11, wherein the smartpad is in a landscape orportrait orientation.

15. The method of aspect 11, wherein toggling between a single and adual application mode toggles which of the two applications is shown,wherein in the single application mode, one application is shown on thefull display.

16. The method of aspect 11, wherein toggling between a single and adual application mode toggles which of the two applications is shown,wherein in the dual application mode, the two applications are shown onthe full display with the seam.

17. The method of aspect 16, wherein an indication is provided to theuser indicating whether the smartpad is in the single or the dualapplication mode.

18. The method of aspect 11, wherein upon receipt of an incoming call onthe smartpad in dual application mode, an incoming call application islaunched on a primary portion of the display.

19. The method of aspect 11, wherein upon receipt of an incoming call onthe smartpad in single application mode, an incoming call application islaunched on a primary portion of the display after the smartpad switchesto dual application mode.

20. The method of aspect 11, wherein upon receipt of an incoming call onthe smartpad in single application mode, an incoming call application islaunched on a primary portion of the display after the smartpad switchesto dual application mode and the seam is placed between the primaryportion and a secondary portion showing a minimized second application.

Additional exemplary aspects are directed toward:

1. A smartpad comprising:

an interface adapted to receive a multi-screen device, content from themulti-screen device displayable on a display of the smartpad; and

an interaction module, the interaction module adapted to provide anindication to a user of an interaction with one or more hardwarefeatures of the one or more of the smartpad and the multi-screen device.

2. The smartpad of aspect 1, wherein the hardware features include oneor more of a power button, a headphone jack, a power adapter, a memorycard slot, a volume button, a mute button and a brightness button on thesmartpad.

3. The smartpad of aspect 1, wherein the hardware features include oneor more of a power button, a headphone jack, a power adapter, a memorycard slot, a volume button, a mute button and a brightness button on themulti-screen device.

4. The smartpad of aspect 1, wherein the indication is one or more of avisual, audible and tactile indication.

5. The smartpad of aspect 1, wherein at least one of the hardwarefeatures on the multi-screen device is accessible to a user when themulti-screen device is docked with the smartpad.

6. The smartpad of aspect 1, wherein the one or more hardware featuresof the multi-screen device control operation of the smartpad.

7. The smartpad of aspect 1, wherein one or more o the one or morehardware features of the multi-screen device control operation are notsupported by the smartpad.

8. The smartpad of aspect 1, wherein one or more o the one or morehardware features of the multi-screen device control operation are notsupported by the smartpad, and one or more of a visual, audible andtactile indication is provided to a user indicating the lack of support.

9. The smartpad of aspect 1, further comprising a communications linkbetween the smartpad and the multi-screen device.

10. The smartpad of aspect 1, wherein the indication is a graphicalpresentation on the display.

11. A method for operating a smartpad comprising:

providing an indication to a user of an interaction with one or morehardware features of the one or more of the smartpad and themulti-screen device while the smartpad and a multi-screen device are ina docked state, the docked state allowing content from the multi-screendevice to be displayed on a display of the smartpad.

12. The method of aspect 11, wherein the hardware features include oneor more of a power button, a headphone jack, a power adapter, a memorycard slot, a volume button, a mute button and a brightness button on thesmartpad.

13. The method of aspect 11, wherein the hardware features include oneor more of a power button, a headphone jack, a power adapter, a memorycard slot, a volume button, a mute button and a brightness button on themulti-screen device.

14. The method of aspect 11, wherein the indication is one or more of avisual, audible and tactile indication.

15. The method of aspect 11, wherein at least one of the hardwarefeatures on the multi-screen device is accessible to a user when themulti-screen device is docked with the smartpad.

16. The method of aspect 11, wherein the one or more hardware featuresof the multi-screen device control operation of the smartpad.

17. The method of aspect 11, wherein one or more o the one or morehardware features of the multi-screen device control operation are notsupported by the smartpad.

18. The method of aspect 11, wherein one or more o the one or morehardware features of the multi-screen device control operation are notsupported by the smartpad, and one or more of a visual, audible andtactile indication is provided to a user indicating the lack of support.

19. The method of aspect 11, further comprising establishing acommunications link between the smartpad and the multi-screen device.

20. The method of aspect 11, wherein the indication is a graphicalpresentation on the display.

Exemplary aspects are also directed toward:

1. A smartpad comprising:

a display, the display adapted to display content from a dockedmulti-screen device; and

a battery measurement module, the battery measurement module adapted tocontrol one or more of charging and power consumption of the smartpad.

2. The smartpad of aspect 1, further comprising a second batterymeasurement module adapted to control one or more of charging and powerconsumption of the smartpad.

3. The smartpad of aspect 1, wherein the battery measurement modulefurther controls one or more of charging and power consumption of themulti-screen device.

4. The smartpad of aspect 2, wherein the battery measurement modulefurther controls one or more of charging and power consumption of thesmartpad.

5. The smartpad of aspect 1, wherein, based on a threshold, power issent from the smartpad to the multi-screen device.

6. The smartpad of aspect 1, wherein, based on a threshold, the smartpadis charged.

7. The smartpad of aspect 1, wherein power is received from a powerport.

8. The smartpad of aspect 1, wherein the battery measurement moduledynamically and automatically determines which of the smartpad andmulti-screen device are to receive power.

9. The smartpad of aspect 1, wherein battery power between the smartpadand the multi-screen device can be shared.

10. The smartpad of aspect 1, wherein a user preference controls one ormore aspects of the battery measurement module.

11. A method for managing power comprising:

controlling one or more of charging and power consumption of a smartpad,the smartpad adapted to display content from a docked multi-screendevice on a display.

12. The method of aspect 11, further comprising a second batterymeasurement module adapted to control one or more of charging and powerconsumption of the smartpad.

13. The method of aspect 11, wherein the battery measurement modulefurther controls one or more of charging and power consumption of themulti-screen device.

14. The method of aspect 12, wherein the battery measurement modulefurther controls one or more of charging and power consumption of thesmartpad.

15. The method of aspect 11, wherein, based on a threshold, power issent from the smartpad to the multi-screen device.

16. The method of aspect 11, wherein, based on a threshold, the smartpadis charged.

17. The method of aspect 11, wherein power is received from a powerport.

18. The method of aspect 11, wherein the battery measurement moduledynamically and automatically determines which of the smartpad andmulti-screen device are to receive power.

19. The method of aspect 11, wherein battery power between the smartpadand the multi-screen device can be shared.

20. The method of aspect 11, wherein a user preference controls one ormore aspects of the battery measurement module.

Exemplary aspects are also directed toward a further embodiment for:

1. A smartpad comprising:

a window stack, the window stack providing visibility into one or moreapplications other than an active application, and allowing managementof the active and the one or more applications;

a screen capture, the screen capture including a representation of theone or more applications; and

a display controller, the display controller adapted to one or more ofresize and reorient the screen capture upon docking of a multi-screendevice to the smartpad.

2. The smartpad of aspect 1, wherein the display controller furthercrops or clips the screen capture.

3. The smartpad of aspect 1, wherein suspended application screencapture treatment is applied to the screen capture.

4. The smartpad of aspect 1, wherein there is a screen capture for eachof the one or more applications in the window stack.

5. The smartpad of aspect 1, wherein the screen captures are edited tolessen differences in screen sizes, orientations, content andorientation.

6. The smartpad of aspect 5, wherein the editing is performed during thedocking.

7. The smartpad of aspect 1, wherein the one or more applications aresuspended applications capable of being reactivated and moved onto adisplay of the smartpad.

8. The smartpad of aspect 7, wherein the suspended applications undergoa crop and clip upon revealing on the display.

9. The smartpad of aspect 1, wherein the smartpad is in a singleapplication mode or a dual application mode, and is in a portrait orlandscape orientation.

10. The smartpad of aspect 1, wherein the multi-screen device is in asingle application mode or a dual application mode, and is in a portraitor landscape orientation.

11. A method for controlling a display on a smartpad comprising:

providing visibility into one or more applications other than an activeapplication, and allowing management of the active and the one or moreapplications via a window stack;

providing a representation of the one or more applications wherein therepresentation is a screen capture; and

one or more of resizing and reorienting the screen capture upon dockingof a multi-screen device to the smartpad.

12. The method of aspect 11, wherein the display controller furthercrops or clips the screen capture.

13. The method of aspect 11, wherein suspended application screencapture treatment is applied to the screen capture.

14. The method of aspect 11, wherein there is a screen capture for eachof the one or more applications in the window stack.

15. The smartpad of aspect 1, wherein the screen captures are edited tolessen differences in screen sizes, orientations, content andorientation.

16. The method of aspect 15, wherein the editing is performed during thedocking.

17. The method of aspect 11, wherein the one or more applications aresuspended applications capable of being reactivated and moved onto adisplay of the smartpad.

18. The method of aspect 17, wherein the suspended applications undergoa crop and clip upon revealing on the display.

19. The method of aspect 11, wherein the smartpad is in a singleapplication mode or a dual application mode, and is in a portrait orlandscape orientation.

20. The method of aspect 11, wherein the multi-screen device is in asingle application mode or a dual application mode, and is in a portraitor landscape orientation.

Even further aspects are directed toward a non-transitorycomputer-readable information storage media having stored thereoninstructions, that when executed by one or more processors, are capableof performing any of the above methods.

These and other advantages will be apparent from the disclosure.

The phrases “at least one”, “one or more”, and “and/or” are open-endedexpressions that are both conjunctive and disjunctive in operation. Forexample, each of the expressions “at least one of A, B and C”, “at leastone of A, B, or C”, “one or more of A, B, and C”, “one or more of A, B,or C” and “A, B, and/or C” means A alone, B alone, C alone, A and Btogether, A and C together, B and C together, or A, B and C together.

The term “a” or “an” entity refers to one or more of that entity. Assuch, the terms “a” (or “an”), “one or more” and “at least one” can beused interchangeably herein. It is also to be noted that the terms“comprising”, “including”, and “having” can be used interchangeably.

The term “automatic” and variations thereof, as used herein, refers toany process or operation done without material human input when theprocess or operation is performed. However, a process or operation canbe automatic, even though performance of the process or operation usesmaterial or immaterial human input, if the input is received beforeperformance of the process or operation. Human input is deemed to bematerial if such input influences how the process or operation will beperformed. Human input that consents to the performance of the processor operation is not deemed to be “material”.

The term “computer-readable medium” as used herein refers to anytangible storage and/or transmission medium that participate inproviding instructions to a processor for execution. Such a medium maytake many forms, including but not limited to, non-volatile media,volatile media, and transmission media. Non-volatile media includes, forexample, NVRAM, or magnetic or optical disks. Volatile media includesdynamic memory, such as main memory. Common forms of computer-readablemedia include, for example, a floppy disk, a flexible disk, hard disk,magnetic tape, or any other magnetic medium, magneto-optical medium, aCD-ROM, any other optical medium, punch cards, paper tape, any otherphysical medium with patterns of holes, a RAM, a PROM, and EPROM, aFLASH-EPROM, a solid state medium like a memory card, any other memorychip or cartridge, a carrier wave as described hereinafter, or any othermedium from which a computer can read. A digital file attachment toe-mail or other self-contained information archive or set of archives isconsidered a distribution medium equivalent to a tangible storagemedium. When the computer-readable media is configured as a database, itis to be understood that the database may be any type of database, suchas relational, hierarchical, object-oriented, and/or the like.Accordingly, the disclosure is considered to include a tangible storagemedium or distribution medium and prior art-recognized equivalents andsuccessor media, in which the software implementations of the presentdisclosure are stored.

The term “desktop” refers to a metaphor used to portray systems. Adesktop is generally considered a “surface” that typically includespictures, called icons, widgets, folders, etc. that can activate showapplications, windows, cabinets, files, folders, documents, and othergraphical items. The icons are generally selectable to initiate a taskthrough user interface interaction to allow a user to executeapplications or conduct other operations.

The term “screen,” “touch screen,” or “touchscreen” refers to a physicalstructure that includes one or more hardware components that provide thedevice with the ability to render a user interface and/or receive userinput. A screen can encompass any combination of gesture capture region,a touch sensitive display, and/or a configurable area. The device canhave one or more physical screens embedded in the hardware. However ascreen may also include an external peripheral device that may beattached and detached from the device. In embodiments, multiple externaldevices may be attached to the device. Thus, in embodiments, the screencan enable the user to interact with the device by touching areas on thescreen and provides information to a user through a display. The touchscreen may sense user contact in a number of different ways, such as bya change in an electrical parameter (e.g., resistance or capacitance),acoustic wave variations, infrared radiation proximity detection, lightvariation detection, and the like. In a resistive touch screen, forexample, normally separated conductive and resistive metallic layers inthe screen pass an electrical current. When a user touches the screen,the two layers make contact in the contacted location, whereby a changein electrical field is noted and the coordinates of the contactedlocation calculated. In a capacitive touch screen, a capacitive layerstores electrical charge, which is discharged to the user upon contactwith the touch screen, causing a decrease in the charge of thecapacitive layer. The decrease is measured, and the contacted locationcoordinates determined. In a surface acoustic wave touch screen, anacoustic wave is transmitted through the screen, and the acoustic waveis disturbed by user contact. A receiving transducer detects the usercontact instance and determines the contacted location coordinates.

The term “display” refers to a portion of one or more screens used todisplay the output of a computer to a user. A display may be asingle-screen display or a multi-screen display, referred to as acomposite display. A composite display can encompass the touch sensitivedisplay of one or more screens. A single physical screen can includemultiple displays that are managed as separate logical displays. Thus,different content can be displayed on the separate displays althoughpart of the same physical screen.

The term “displayed image” refers to an image produced on the display. Atypical displayed image is a window or desktop. The displayed image mayoccupy all or a portion of the display.

The term “display orientation” refers to the way in which a rectangulardisplay is oriented by a user for viewing. The two most common types ofdisplay orientation are portrait and landscape. In landscape mode, thedisplay is oriented such that the width of the display is greater thanthe height of the display (such as a 4:3 ratio, which is 4 units wideand 3 units tall, or a 16:9 ratio, which is 16 units wide and 9 unitstall). Stated differently, the longer dimension of the display isoriented substantially horizontal in landscape mode while the shorterdimension of the display is oriented substantially vertical. In theportrait mode, by contrast, the display is oriented such that the widthof the display is less than the height of the display. Stateddifferently, the shorter dimension of the display is orientedsubstantially horizontal in the portrait mode while the longer dimensionof the display is oriented substantially vertical.

The term “composited display” refers to a logical structure that definesa display that can encompass one or more screens. A multi-screen displaycan be associated with a composite display that encompasses all thescreens. The composite display can have different displaycharacteristics based on the various orientations of the device.

The term “gesture” refers to a user action that expresses an intendedidea, action, meaning, result, and/or outcome. The user action caninclude manipulating a device (e.g., opening or closing a device,changing a device orientation, moving a trackball or wheel, etc.),movement of a body part in relation to the device, movement of animplement or tool in relation to the device, audio inputs, etc. Agesture may be made on a device (such as on the screen) or with thedevice to interact with the device.

The term “module” as used herein refers to any known or later developedhardware, software, firmware, artificial intelligence, fuzzy logic, orcombination of hardware and software that is capable of performing thefunctionality associated with that element.

The term “gesture capture” refers to a sense or otherwise a detection ofan instance and/or type of user gesture. The gesture capture can occurin one or more areas of the screen, A gesture region can be on thedisplay, where it may be referred to as a touch sensitive display or offthe display where it may be referred to as a gesture capture area.

A “multi-screen application” refers to an application that is capable ofmultiple modes. The multi-screen application mode can include, but isnot limited to, a single screen mode (where the application is displayedon a single screen) or a composite display mode (where the applicationis displayed on two or more screens). A multi-screen application canhave different layouts optimized for the mode. Thus, the multi-screenapplication can have different layouts for a single screen or for acomposite display that can encompass two or more screens. The differentlayouts may have different screen/display dimensions and/orconfigurations on which the user interfaces of the multi-screenapplications can be rendered. The different layouts allow theapplication to optimize the application's user interface for the type ofdisplay, e.g., single screen or multiple screens. In single screen mode,the multi-screen application may present one window pane of information.In a composite display mode, the multi-screen application may presentmultiple window panes of information or may provide a larger and aricher presentation because there is more space for the displaycontents. The multi-screen applications may be designed to adaptdynamically to changes in the device and the mode depending on whichdisplay (single or composite) the system assigns to the multi-screenapplication. In alternative embodiments, the user can use a gesture torequest the application transition to a different mode, and, if adisplay is available for the requested mode, the device can allow theapplication to move to that display and transition modes.

A “single-screen application” refers to an application that is capableof single screen mode. Thus, the single-screen application can produceonly one window and may not be capable of different modes or differentdisplay dimensions. A single-screen application may not be capable ofthe several modes discussed with the multi-screen application.

The term “window” refers to a, typically rectangular, displayed image onat least part of a display that contains or provides content differentfrom the rest of the screen. The window may obscure the desktop.

The terms “determine”, “calculate” and “compute,” and variationsthereof, as used herein, are used interchangeably and include any typeof methodology, process, mathematical operation or technique.

It shall be understood that the term “means” as used herein shall begiven its broadest possible interpretation in accordance with 35 U.S.C.,Section 112, Paragraph 6. Accordingly, a claim incorporating the term“means” shall cover all structures, materials, or acts set forth herein,and all of the equivalents thereof. Further, the structures, materialsor acts and the equivalents thereof shall include all those described inthe summary of the invention, brief description of the drawings,detailed description, abstract, and claims themselves.

The preceding is a simplified summary of the disclosure to provide anunderstanding of some aspects of the disclosure. This summary is neitheran extensive nor exhaustive overview of the disclosure and its variousaspects, embodiments, and/or configurations. It is intended neither toidentify key or critical elements of the disclosure nor to delineate thescope of the disclosure but to present selected concepts of thedisclosure in a simplified form as an introduction to the more detaileddescription presented below. As will be appreciated, other aspects,embodiments, and/or configurations of the disclosure are possibleutilizing, alone or in combination, one or more of the features setforth above or described in detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A includes a first view of an embodiment of a multi-screen userdevice;

FIG. 1B includes a second view of an embodiment of a multi-screen userdevice;

FIG. 1C includes a third view of an embodiment of a multi-screen userdevice;

FIG. 1D includes a fourth view of an embodiment of a multi-screen userdevice;

FIG. 1E includes a fifth view of an embodiment of a multi-screen userdevice;

FIG. 1F includes a sixth view of an embodiment of a multi-screen userdevice;

FIG. 1G includes a seventh view of an embodiment of a multi-screen userdevice;

FIG. 1H includes a eighth view of an embodiment of a multi-screen userdevice;

FIG. 1I includes a ninth view of an embodiment of a multi-screen userdevice;

FIG. 1J includes a tenth view of an embodiment of a multi-screen userdevice;

FIG. 2 is a block diagram of an embodiment of the hardware of thedevice;

FIG. 3A is a block diagram of an embodiment of the state model for thedevice based on the device's orientation and/or configuration;

FIG. 3B is a table of an embodiment of the state model for the devicebased on the device's orientation and/or configuration;

FIG. 4A is a first representation of an embodiment of user gesturereceived at a device;

FIG. 4B is a second representation of an embodiment of user gesturereceived at a device;

FIG. 4C is a third representation of an embodiment of user gesturereceived at a device;

FIG. 4D is a fourth representation of an embodiment of user gesturereceived at a device;

FIG. 4E is a fifth representation of an embodiment of user gesturereceived at a device;

FIG. 4F is a sixth representation of an embodiment of user gesturereceived at a device;

FIG. 4G is a seventh representation of an embodiment of user gesturereceived at a device;

FIG. 4H is a eighth representation of an embodiment of user gesturereceived at a device;

FIG. 5A is a block diagram of an embodiment of the device softwareand/or firmware;

FIG. 5B is a second block diagram of an embodiment of the devicesoftware and/or firmware;

FIG. 6A is a first representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6B is a second representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6C is a third representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6D is a fourth representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6E is a fifth representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6F is a sixth representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6G is a seventh representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6H is a eighth representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6I is a ninth representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6J is a tenth representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 7A is representation of a logical window stack;

FIG. 7B is another representation of an embodiment of a logical windowstack;

FIG. 7C is another representation of an embodiment of a logical windowstack;

FIG. 7D is another representation of an embodiment of a logical windowstack;

FIG. 7E is another representation of an embodiment of a logical windowstack;

FIG. 8 is block diagram of an embodiment of a logical data structure fora window stack;

FIG. 9 is a flow chart of an embodiment of a method for creating awindow stack;

FIG. 10 illustrates an exemplary smartpad (SP).

FIG. 11 illustrates an exemplary method of associating the smartpad withthe device.

FIG. 12 illustrates a docked device with the smartpad.

FIGS. 13A-13B illustrate an exemplary method for screen orientation.

FIG. 14 illustrates a method for displaying an application when the SPis in a landscape mode.

FIG. 15 illustrates a method for displaying an application when the SPis in a portrait mode.

FIG. 16 illustrates an example of a dual screen application in portraitmax mode.

FIG. 17 illustrates an example of a dual screen application in max modelandscape.

FIG. 18 illustrates an example of keyboard management on the SP.

FIG. 19 illustrates an example of keyboard management on the SP with anapplication area in max mode.

FIG. 20 illustrates another example of keyboard management for the SP inlandscape mode.

FIG. 21 illustrates an example of a dual screen application running in adual screen emulation mode on the SP with a virtual keyboard.

FIG. 22 illustrates an example of application window stack management onthe SP.

FIG. 23 illustrates another example of application window stackmanagement on the SP.

FIG. 24 illustrates an example of multi application mode of the SP,wherein in the multi application mode the SP emulates the device in itsmini-tablet form.

FIG. 25 illustrates another example of multi application mode of the SP.

FIG. 26 illustrates another example of multi application mode of the SP.

FIG. 27 illustrates another example of multi application mode of the SP.

FIG. 28 illustrates a method for managing screen display.

FIG. 29 illustrates an exemplary method for managing screen display withthe desktop.

FIG. 30 illustrates an exemplary method of managing screen display witha keyboard.

FIGS. 31A and 31B illustrate desktop management on the SP.

FIGS. 32A and 32B illustrate exemplary methods for desktop panelmanagement.

FIG. 33 illustrates exemplary notification management on the SP.

FIGS. 34A and 34B illustrate exemplary techniques for applicationmanagement.

FIGS. 35A and 35B illustrate an exemplary method for providing desktoppreviews or hints.

FIG. 36 illustrates an exemplary carousel application window stack.

FIG. 37 illustrates an exemplary carousel application window stack witha virtual keyboard.

FIG. 38 illustrates an exemplary method for associating the device andthe SP.

FIG. 39 illustrates an exemplary method for application reorientationbased on SP orientation.

FIG. 40 illustrates an exemplary method for managing the keyboard on theSP.

FIG. 41 illustrates an exemplary method for window manipulation based onone or more gestures.

FIG. 42 illustrates an exemplary method for application highlightingwhen an application is in focus in multi application mode.

FIG. 43 illustrates an exemplary method for application maximization.

FIG. 44 illustrates an exemplary method for transitioning from anapplication window to the desktop.

FIG. 45 illustrates an exemplary method for managing the display of thedesktop and/or one or more panels on the SP.

FIG. 46 illustrates an exemplary method for merging panels for displayon the SP.

FIG. 47 illustrates an exemplary method for previewing one or morepanels on the SP.

FIG. 48 illustrates an exemplary method for stack management in multiapplication mode.

FIG. 49 illustrates exemplary device and SP hardware and docking.

FIG. 50A illustrates exemplary device and SP hardware and docking.

FIG. 50B illustrates exemplary device and SP hardware and docking andscreen management.

FIG. 51 illustrates exemplary SP power management.

FIG. 52 illustrates exemplary SP power management.

FIG. 53 illustrates exemplary SP power management and status indicators.

FIG. 54 illustrates exemplary SP power management icons and states.

FIG. 55 illustrates an exemplary keyboard configuration.

FIG. 56 illustrates another exemplary keyboard configuration.

FIG. 57 illustrates an exemplary keyboard configuration in landscapemode.

FIG. 58 illustrates an exemplary keyboard configuration in landscapemode.

FIG. 59 illustrates an exemplary keyboard and slider configuration.

FIG. 60 illustrates another exemplary keyboard and slider configuration.

FIG. 61 illustrates another exemplary keyboard and slider configuration.

FIG. 62 illustrates another exemplary keyboard and slider configuration.

FIG. 63 illustrates another exemplary keyboard and slider configuration.

FIG. 64 illustrates another exemplary keyboard and slider configuration.

FIG. 65 illustrates another exemplary keyboard and slider configuration.

FIG. 66 illustrates another exemplary keyboard and slider configuration.

FIG. 67 illustrates another exemplary keyboard and slider configuration.

FIG. 68 illustrates exemplary window stack management.

FIG. 69 illustrates exemplary window stack management.

FIG. 70 illustrates exemplary window/application management upondocking.

FIG. 71 illustrates exemplary window/application window management upondocking.

FIG. 72 illustrates exemplary window/application window management upondocking.

FIG. 73 illustrates exemplary window/application window management upondocking.

FIG. 74 illustrates exemplary window/application window management upondocking.

FIG. 75 illustrates exemplary window/application window management upondocking.

FIG. 76 illustrates exemplary window/application window management upondocking.

FIG. 77 illustrates exemplary window/application window management upondocking.

FIG. 78 illustrates exemplary window/application window management upondocking.

FIG. 79 illustrates exemplary window/application window management upondocking.

FIG. 80 illustrates exemplary window/application window management upondocking.

FIG. 81 illustrates exemplary window/application window management upondocking.

FIG. 82 illustrates exemplary window/application window management upondocking.

FIG. 83 illustrates exemplary window/application window management upondocking.

FIG. 84 illustrates exemplary window management after docking.

FIG. 85 illustrates exemplary window management after docking.

FIG. 86 illustrates exemplary window management.

FIG. 87 illustrates exemplary window management.

FIG. 88 illustrates exemplary application management.

FIG. 89 illustrates exemplary application management.

FIG. 90 illustrates exemplary application management.

FIG. 91 illustrates exemplary application management.

FIG. 92 illustrates exemplary application management.

FIG. 93 illustrates exemplary application/desktop management.

FIG. 94 illustrates an exemplary keyboard/application configuration.

FIG. 95 illustrates an exemplary stack management.

FIG. 96 illustrates exemplary seam/focus/application/display/stackmanagement.

FIG. 97 illustrates exemplary seam/focus/application/display/stackmanagement.

FIG. 98 illustrates exemplary seam/focus/application/display/stackmanagement.

FIG. 99 illustrates exemplary seam/focus/application/display/stackmanagement.

FIG. 100 illustrates exemplary seam/focus/application/display/stackmanagement.

FIG. 101 illustrates exemplary seam/focus/application/display/stackmanagement.

FIG. 102 illustrates exemplary seam/focus/application/display/stackmanagement.

FIG. 103 illustrates exemplary seam/focus/application/display/stackmanagement.

FIG. 104 illustrates exemplary seam/focus/application/display/stackmanagement.

FIG. 105 illustrates exemplary seam/focus/application/display/stackmanagement.

FIG. 106 illustrates exemplary seam/focus/application/display/stackmanagement.

FIG. 107 illustrates exemplary seam/focus/application/display/stackmanagement.

FIG. 108 illustrates exemplary seam/focus/application/display/stackmanagement.

FIG. 109 illustrates exemplary seam/focus/application/display/stackmanagement.

FIG. 110 illustrates exemplary seam/focus/application/display/stackmanagement.

FIG. 111 illustrates exemplary seam/focus/application/display/stackmanagement.

FIG. 112 illustrates exemplary seam/focus/application/display/stackmanagement.

FIG. 113 illustrates exemplary seam/focus/application/display/stackmanagement.

FIG. 114 illustrates exemplary seam/focus/application/display/stackmanagement.

FIG. 115 illustrates exemplary seam/focus/application/display/stackmanagement.

FIG. 116 illustrates an exemplary call management technique.

FIG. 117 illustrates an exemplary call management technique.

FIG. 118 illustrates an exemplary call management technique.

FIG. 119 illustrates an exemplary call management technique.

FIG. 120 illustrates an exemplary notification configuration.

FIG. 121 illustrates another exemplary notification configuration.

FIG. 122 illustrates an exemplary cross-device hardware buttonrecognition configuration.

FIG. 123 illustrates an exemplary power management configuration.

FIG. 124 illustrates an exemplary method for power management.

FIG. 125 illustrates an exemplary screen snapshot management technique.

FIG. 126 illustrates an exemplary method for managing and resizingscreen captures.

FIG. 127 illustrates an exemplary configuration for harmonizingdisplayed images.

FIG. 128 illustrates an exemplary composited application screen.

FIG. 129 illustrates an exemplary composited application screen.

FIG. 130 illustrates an exemplary technique forscaling/clipping/resizing.

FIG. 131 illustrates an exemplary technique forscaling/clipping/resizing.

FIG. 132 illustrates an exemplary technique for power management.

FIG. 133 illustrates an exemplary technique for managing a keyboard andslider bar.

FIG. 134 illustrates an exemplary technique for managing focus.

FIG. 135 illustrates an exemplary technique for managing applicationdisplay.

FIG. 136 illustrates an exemplary technique for managing applicationdisplay.

FIG. 137 illustrates an exemplary technique for managing applicationdisplay.

FIG. 138 illustrates an exemplary technique for managing applicationdisplay.

FIG. 139 illustrates an exemplary technique for managing applicationdisplay.

FIG. 140 illustrates an exemplary technique for providing feedback basedon hardware interaction.

In the appended figures, similar components and/or features may have thesame reference label. Further, various components of the same type maybe distinguished by following the reference label by a letter thatdistinguishes among the similar components. If only the first referencelabel is used in the specification, the description is applicable to anyone of the similar components having the same first reference labelirrespective of the second reference label.

DETAILED DESCRIPTION

Presented herein are embodiments of a device. The device can be acommunications device, such as a cellular telephone, or other smartdevice. The device can include two screens that are oriented to provideseveral unique display configurations. Further, the device can receiveuser input in unique ways. The overall design and functionality of thedevice provides for an enhanced user experience making the device moreuseful and more efficient.

Mechanical Features:

FIGS. 1A-1J illustrate a device 100 in accordance with embodiments ofthe present disclosure. As described in greater detail below, device 100can be positioned in a number of different ways each of which providesdifferent functionality to a user. The device 100 is a multi-screendevice that includes a primary screen 104 and a secondary screen 108,both of which are touch sensitive. In embodiments, the entire frontsurface of screens 104 and 108 may be touch sensitive and capable ofreceiving input by a user touching the front surface of the screens 104and 108. Primary screen 104 includes touch sensitive display 110, which,in addition to being touch sensitive, also displays information to auser. Secondary screen 108 includes touch sensitive display 114, whichalso displays information to a user. In other embodiments, screens 104and 108 may include more than one display area.

Primary screen 104 also includes a configurable area 112 that has beenconfigured for specific inputs when the user touches portions of theconfigurable area 112. Secondary screen 108 also includes a configurablearea 116 that has been configured for specific inputs. Areas 112 a and116 a have been configured to receive a “back” input indicating that auser would like to view information previously displayed. Areas 112 band 116 b have been configured to receive a “menu” input indicating thatthe user would like to view options from a menu. Areas 112 c and 116 chave been configured to receive a “home” input indicating that the userwould like to view information associated with a “home” view. In otherembodiments, areas 112 a-c and 116 a-c may be configured, in addition tothe configurations described above, for other types of specific inputsincluding controlling features of device 100, some non-limiting examplesincluding adjusting overall system power, adjusting the volume,adjusting the brightness, adjusting the vibration, selecting ofdisplayed items (on either of screen 104 or 108), operating a camera,operating a microphone, and initiating/terminating of telephone calls.Also, in some embodiments, areas 112 a-C and 116 a-C may be configuredfor specific inputs depending upon the application running on device 100and/or information displayed on touch sensitive displays 110 and/or 114.

In addition to touch sensing, primary screen 104 and secondary screen108 may also include areas that receive input from a user withoutrequiring the user to touch the display area of the screen. For example,primary screen 104 includes gesture capture area 120, and secondaryscreen 108 includes gesture capture area 124. These areas are able toreceive input by recognizing gestures made by a user without the needfor the user to actually touch the surface of the display area. Incomparison to touch sensitive displays 110 and 114, the gesture captureareas 120 and 124 are commonly not capable of rendering a displayedimage.

The two screens 104 and 108 are connected together with a hinge 128,shown clearly in FIG. 1C (illustrating a back view of device 100). Hinge128, in the embodiment shown in FIGS. 1A-1J, is a center hinge thatconnects screens 104 and 108 so that when the hinge is closed, screens104 and 108 are juxtaposed (i.e., side-by-side) as shown in FIG. 1B(illustrating a front view of device 100). Hinge 128 can be opened toposition the two screens 104 and 108 in different relative positions toeach other. As described in greater detail below, the device 100 mayhave different functionalities depending on the relative positions ofscreens 104 and 108.

FIG. 1D illustrates the right side of device 100. As shown in FIG. 1D,secondary screen 108 also includes a card slot 132 and a port 136 on itsside. Card slot 132 in embodiments, accommodates different types ofcards including a subscriber identity module (SIM). Port 136 inembodiments is an input/output port (I/O port) that allows device 100 tobe connected to other peripheral devices, such as a display, keyboard,or printing device. As can be appreciated, these are merely someexamples and in other embodiments device 100 may include other slots andports such as slots and ports for accommodating additional memorydevices and/or for connecting other peripheral devices. Also shown inFIG. 1D is an audio jack 140 that accommodates a tip, ring, sleeve (TRS)connector for example to allow a user to utilize headphones or aheadset.

Device 100 also includes a number of buttons 158. For example, FIG. 1Eillustrates the left side of device 100. As shown in FIG. 1E, the sideof primary screen 104 includes three buttons 144, 148, and 152, whichcan be configured for specific inputs. For example, buttons 144, 148,and 152 may be configured to, in combination or alone, control a numberof aspects of device 100. Some non-limiting examples include overallsystem power, volume, brightness, vibration, selection of displayeditems (on either of screen 104 or 108), a camera, a microphone, andinitiation/termination of telephone calls. In some embodiments, insteadof separate buttons two buttons may be combined into a rocker button.This arrangement is useful in situations where the buttons areconfigured to control features such as volume or brightness. In additionto buttons 144, 148, and 152, device 100 also includes a button 156,shown in FIG. 1F, which illustrates the top of device 100. In oneembodiment, button 156 is configured as an on/off button used to controloverall system power to device 100. In other embodiments, button 156 isconfigured to, in addition to or in lieu of controlling system power,control other aspects of device 100. In some embodiments, one or more ofthe buttons 144, 148, 152, and 156 are capable of supporting differentuser commands. By way of example, a normal press has a duration commonlyof less than about 1 second and resembles a quick tap. A medium presshas a duration commonly of 1 second or more but less than about 12seconds. A long press has a duration commonly of about 12 seconds ormore. The function of the buttons is normally specific to theapplication that is currently in focus on the respective display 110 and114. In a telephone application for instance and depending on theparticular button, a normal, medium, or long press can mean end call,increase in call volume, decrease in call volume, and toggle microphonemute. In a camera or video application for instance and depending on theparticular button, a normal, medium, or long press can mean increasezoom, decrease zoom, and take photograph or record video.

There are also a number of hardware components within device 100. Asillustrated in FIG. 1C, device 100 includes a speaker 160 and amicrophone 164. Device 100 also includes a camera 168 (FIG. 1B).Additionally, device 100 includes two position sensors 172A and 172B,which are used to determine the relative positions of screens 104 and108. In one embodiment, position sensors 172A and 172B are Hall effectsensors. However, in other embodiments other sensors can be used inaddition to or in lieu of the Hall effect sensors. An accelerometer 176may also be included as part of device 100 to determine the orientationof the device 100 and/or the orientation of screens 104 and 108.Additional internal hardware components that may be included in device100 are described below with respect to FIG. 2.

The overall design of device 100 allows it to provide additionalfunctionality not available in other communication devices. Some of thefunctionality is based on the various positions and orientations thatdevice 100 can have. As shown in FIGS. 1B-1G, device 100 can be operatedin an “open” position where screens 104 and 108 are juxtaposed. Thisposition allows a large display area for displaying information to auser. When position sensors 172A and 172B determine that device 100 isin the open position, they can generate a signal that can be used totrigger different events such as displaying information on both screens104 and 108. Additional events may be triggered if accelerometer 176determines that device 100 is in a portrait position (FIG. 1B) asopposed to a landscape position (not shown).

In addition to the open position, device 100 may also have a “closed”position illustrated in FIG. 1H. Again, position sensors 172A and 172Bcan generate a signal indicating that device 100 is in the “closed”position. This can trigger an event that results in a change ofdisplayed information on screen 104 and/or 108. For example, device 100may be programmed to stop displaying information on one of the screens,e.g., screen 108, since a user can only view one screen at a time whendevice 100 is in the “closed” position. In other embodiments, the signalgenerated by position sensors 172A and 172B, indicating that the device100 is in the “closed” position, can trigger device 100 to answer anincoming telephone call. The “closed” position can also be a preferredposition for utilizing the device 100 as a mobile phone.

Device 100 can also be used in an “easel” position which is illustratedin FIG. 1I. In the “easel” position, screens 104 and 108 are angled withrespect to each other and facing outward with the edges of screens 104and 108 substantially horizontal. In this position, device 100 can beconfigured to display information on both screens 104 and 108 to allowtwo users to simultaneously interact with device 100. When device 100 isin the “easel” position, sensors 172A and 172B generate a signalindicating that the screens 104 and 108 are positioned at an angle toeach other, and the accelerometer 176 can generate a signal indicatingthat device 100 has been placed so that the edge of screens 104 and 108are substantially horizontal. The signals can then be used incombination to generate events that trigger changes in the display ofinformation on screens 104 and 108.

FIG. 1J illustrates device 100 in a “modified easel” position. In the“modified easel” position, one of screens 104 or 108 is used as a standand is faced down on the surface of an object such as a table. Thisposition provides a convenient way for information to be displayed to auser in landscape orientation. Similar to the easel position, whendevice 100 is in the “modified easel” position, position sensors 172Aand 172B generate a signal indicating that the screens 104 and 108 arepositioned at an angle to each other. The accelerometer 176 wouldgenerate a signal indicating that device 100 has been positioned so thatone of screens 104 and 108 is faced downwardly and is substantiallyhorizontal. The signals can then be used to generate events that triggerchanges in the display of information of screens 104 and 108. Forexample, information may not be displayed on the screen that is facedown since a user cannot see the screen.

Transitional states are also possible. When the position sensors 172Aand B and/or accelerometer indicate that the screens are being closed orfolded (from open), a closing transitional state is recognized.Conversely when the position sensors 172A and B indicate that thescreens are being opened or folded (from closed), an openingtransitional state is recognized. The closing and opening transitionalstates are typically time-based, or have a maximum time duration from asensed starting point. Normally, no user input is possible when one ofthe closing and opening states is in effect. In this manner, incidentaluser contact with a screen during the closing or opening function is notmisinterpreted as user input. In embodiments, another transitional stateis possible when the device 100 is closed. This additional transitionalstate allows the display to switch from one screen 104 to the secondscreen 108 when the device 100 is closed based on some user input, e.g.,a double tap on the screen 110,114.

As can be appreciated, the description of device 100 is made forillustrative purposes only, and the embodiments are not limited to thespecific mechanical features shown in FIGS. 1A-1J and described above.In other embodiments, device 100 may include additional features,including one or more additional buttons, slots, display areas, hinges,and/or locking mechanisms. Additionally, in embodiments, the featuresdescribed above may be located in different parts of device 100 andstill provide similar functionality. Therefore, FIGS. 1A-1J and thedescription provided above are nonlimiting.

Hardware Features:

FIG. 2 illustrates components of a device 100 in accordance withembodiments of the present disclosure. In general, the device 100includes a primary screen 104 and a secondary screen 108. While theprimary screen 104 and its components are normally enabled in both theopened and closed positions or states, the secondary screen 108 and itscomponents are normally enabled in the opened state but disabled in theclosed state. However, even when in the closed state a user orapplication triggered interrupt (such as in response to a phoneapplication or camera application operation) can flip the active screen,or disable the primary screen 104 and enable the secondary screen 108,by a suitable command. Each screen 104, 108 can be touch sensitive andcan include different operative areas. For example, a first operativearea, within each touch sensitive screen 104 and 108, may comprise atouch sensitive display 110, 114. In general, the touch sensitivedisplay 110, 114 may comprise a full color, touch sensitive display. Asecond area within each touch sensitive screen 104 and 108 may comprisea gesture capture region 120, 124. The gesture capture region 120, 124may comprise an area or region that is outside of the touch sensitivedisplay 110, 114 area, and that is capable of receiving input, forexample in the form of gestures provided by a user. However, the gesturecapture region 120, 124 does not include pixels that can perform adisplay function or capability.

A third region of the touch sensitive screens 104 and 108 may comprise aconfigurable area 112, 116. The configurable area 112, 116 is capable ofreceiving input and has display or limited display capabilities. Inembodiments, the configurable area 112, 116 may present different inputoptions to the user. For example, the configurable area 112, 116 maydisplay buttons or other relatable items. Moreover, the identity ofdisplayed buttons, or whether any buttons are displayed at all withinthe configurable area 112, 116 of a touch sensitive screen 104 or 108,may be determined from the context in which the device 100 is usedand/or operated. In an exemplary embodiment, the touch sensitive screens104 and 108 comprise liquid crystal display devices extending across atleast those regions of the touch sensitive screens 104 and 108 that arecapable of providing visual output to a user, and a capacitive inputmatrix over those regions of the touch sensitive screens 104 and 108that are capable of receiving input from the user.

One or more display controllers 216 a, 216 b may be provided forcontrolling the operation of the touch sensitive screens 104 and 108,including input (touch sensing) and output (display) functions. In theexemplary embodiment illustrated in FIG. 2, a separate touch screencontroller 216 a or 216 b is provided for each touch screen 104 and 108.In accordance with alternate embodiments, a common or shared touchscreen controller 216 may be used to control each of the included touchsensitive screens 104 and 108. In accordance with still otherembodiments, the functions of a touch screen controller 216 may beincorporated into other components, such as a processor 204.

The processor 204 may comprise a general purpose programmable processoror controller for executing application programming or instructions. Inaccordance with at least some embodiments, the processor 204 may includemultiple processor cores, and/or implement multiple virtual processors.In accordance with still other embodiments, the processor 204 mayinclude multiple physical processors. As a particular example, theprocessor 204 may comprise a specially configured application specificintegrated circuit (ASIC) or other integrated circuit, a digital signalprocessor, a controller, a hardwired electronic or logic circuit, aprogrammable logic device or gate array, a special purpose computer, orthe like. The processor 204 generally functions to run programming codeor instructions implementing various functions of the device 100.

A communication device 100 may also include memory 208 for use inconnection with the execution of application programming or instructionsby the processor 204, and for the temporary or long term storage ofprogram instructions and/or data. As examples, the memory 208 maycomprise RAM, DRAM, SDRAM, or other solid state memory. Alternatively orin addition, data storage 212 may be provided. Like the memory 208, thedata storage 212 may comprise a solid state memory device or devices.Alternatively or in addition, the data storage 212 may comprise a harddisk drive or other random access memory.

In support of communications functions or capabilities, the device 100can include a cellular telephony module 228. As examples, the cellulartelephony module 228 can comprise a GSM, CDMA, FDMA and/or analogcellular telephony transceiver capable of supporting voice, multimediaand/or data transfers over a cellular network. Alternatively or inaddition, the device 100 can include an additional or other wirelesscommunications module 232. As examples, the other wirelesscommunications module 232 can comprise a Wi-Fi, BLUETOOTH™, WiMax,infrared, or other wireless communications link. The cellular telephonymodule 228 and the other wireless communications module 232 can each beassociated with a shared or a dedicated antenna 224.

A port interface 252 may be included. The port interface 252 may includeproprietary or universal ports to support the interconnection of thedevice 100 to other devices or components, such as a dock, which may ormay not include additional or different capabilities from those integralto the device 100. In addition to supporting an exchange ofcommunication signals between the device 100 and another device orcomponent, the docking port 136 and/or port interface 252 can supportthe supply of power to or from the device 100. The port interface 252also comprises an intelligent element that comprises a docking modulefor controlling communications or other interactions between the device100 and a connected device or component.

An input/output module 248 and associated ports may be included tosupport communications over wired networks or links, for example withother communication devices, server devices, and/or peripheral devices.Examples of an input/output module 248 include an Ethernet port, aUniversal Serial Bus (USB) port, Institute of Electrical and ElectronicsEngineers (IEEE) 1394, or other interface.

An audio input/output interface/device(s) 244 can be included to provideanalog audio to an interconnected speaker or other device, and toreceive analog audio input from a connected microphone or other device.As an example, the audio input/output interface/device(s) 244 maycomprise an associated amplifier and analog to digital converter.Alternatively or in addition, the device 100 can include an integratedaudio input/output device 256 and/or an audio jack for interconnectingan external speaker or microphone. For example, an integrated speakerand an integrated microphone can be provided, to support near talk orspeaker phone operations.

Hardware buttons 158 can be included for example for use in connectionwith certain control operations. Examples include a master power switch,volume control, etc., as described in conjunction with FIGS. 1A through1J. One or more image capture interfaces/devices 240, such as a camera,can be included for capturing still and/or video images. Alternativelyor in addition, an image capture interface/device 240 can include ascanner or code reader. An image capture interface/device 240 caninclude or be associated with additional elements, such as a flash orother light source.

The device 100 can also include a global positioning system (GPS)receiver 236. In accordance with embodiments of the present invention,the GPS receiver 236 may further comprise a GPS module that is capableof providing absolute location information to other components of thedevice 100. An accelerometer(s) 176 may also be included. For example,in connection with the display of information to a user and/or otherfunctions, a signal from the accelerometer 176 can be used to determinean orientation and/or format in which to display that information to theuser.

Embodiments of the present invention can also include one or moreposition sensor(s) 172. The position sensor 172 can provide a signalindicating the position of the touch sensitive screens 104 and 108relative to one another. This information can be provided as an input,for example to a user interface application, to determine an operatingmode, characteristics of the touch sensitive displays 110, 114, and/orother device 100 operations. As examples, a screen position sensor 172can comprise a series of Hall effect sensors, a multiple positionswitch, an optical switch, a Wheatstone bridge, a potentiometer, orother arrangement capable of providing a signal indicating of multiplerelative positions the touch screens are in.

Communications between various components of the device 100 can becarried by one or more buses 222. In addition, power can be supplied tothe components of the device 100 from a power source and/or powercontrol module 260. The power control module 260 can, for example,include a battery, an AC to DC converter, power control logic, and/orports for interconnecting the device 100 to an external source of power.

Device State:

FIGS. 3A and 3B represent illustrative states of device 100. While anumber of illustrative states are shown, and transitions from a firststate to a second state, it is to be appreciated that the illustrativestate diagram may not encompass all possible states and/or all possibletransitions from a first state to a second state. As illustrated in FIG.3, the various arrows between the states (illustrated by the staterepresented in the circle) represent a physical change that occurs tothe device 100, that is detected by one or more of hardware andsoftware, the detection triggering one or more of a hardware and/orsoftware interrupt that is used to control and/or manage one or morefunctions of device 100.

As illustrated in FIG. 3A, there are twelve exemplary “physical” states:closed 304, transition 308 (or opening transitional state), easel 312,modified easel 316, open 320, inbound/outbound call or communication324, image/video capture 328, transition 332 (or closing transitionalstate), landscape 340, docked 336, docked 344 and landscape 348. Next toeach illustrative state is a representation of the physical state of thedevice 100 with the exception of states 324 and 328, where the state isgenerally symbolized by the international icon for a telephone and theicon for a camera, respectfully.

In state 304, the device is in a closed state with the device 100generally oriented in the portrait direction with the primary screen 104and the secondary screen 108 back-to-back in different planes (see FIG.1H). From the closed state, the device 100 can enter, for example,docked state 336, where the device 100 is coupled with a dockingstation, docking cable, or in general docked or associated with one ormore other devices or peripherals, or the landscape state 340, where thedevice 100 is generally oriented with the primary screen 104 facing theuser, and the primary screen 104 and the secondary screen 108 beingback-to-back.

In the closed state, the device can also move to a transitional statewhere the device remains closed by the display is moved from one screen104 to another screen 108 based on a user input, e.g., a double tap onthe screen 110, 114. Still another embodiment includes a bilateralstate. In the bilateral state, the device remains closed, but a singleapplication displays at least one window on both the first display 110and the second display 114. The windows shown on the first and seconddisplay 110, 114 may be the same or different based on the applicationand the state of that application. For example, while acquiring an imagewith a camera, the device may display the view finder on the firstdisplay 110 and displays a preview for the photo subjects (full screenand mirrored left-to-right) on the second display 114.

In state 308, a transition state from the closed state 304 to thesemi-open state or easel state 312, the device 100 is shown opening withthe primary screen 104 and the secondary screen 108 being rotated arounda point of axis coincidence with the hinge. Upon entering the easelstate 312, the primary screen 104 and the secondary screen 108 areseparated from one another such that, for example, the device 100 cansit in an easel-like configuration on a surface.

In state 316, known as the modified easel position, the device 100 hasthe primary screen 104 and the secondary screen 108 in a similarrelative relationship to one another as in the easel state 312, with thedifference being one of the primary screen 104 or the secondary screen108 are placed on a surface as shown.

State 320 is the open state where the primary screen 104 and thesecondary screen 108 are generally on the same plane. From the openstate, the device 100 can transition to the docked state 344 or the openlandscape state 348. In the open state 320, the primary screen 104 andthe secondary screen 108 are generally in the portrait-like orientationwhile in landscaped state 348 the primary screen 104 and the secondaryscreen 108 are generally in a landscape-like orientation.

State 324 is illustrative of a communication state, such as when aninbound or outbound call is being received or placed, respectively, bythe device 100. While not illustrated for clarity, it should beappreciated the device 100 can transition to the inbound/outbound callstate 324 from any state illustrated in FIG. 3. In a similar manner, theimage/video capture state 328 can be entered into from any other statein FIG. 3, with the image/video capture state 328 allowing the device100 to take one or more images via a camera and/or videos with a videocapture device 240.

Transition state 322 illustratively shows primary screen 104 and thesecondary screen 108 being closed upon one another for entry into, forexample, the closed state 304.

FIG. 3B illustrates, with reference to the key, the inputs that arereceived to detect a transition from a first state to a second state. InFIG. 3B, various combinations of states are shown with in general, aportion of the columns being directed toward a portrait state 352, alandscape state 356, and a portion of the rows being directed toportrait state 360 and landscape state 364.

In FIG. 3B, the Key indicates that “H” represents an input from one ormore Hall Effect sensors, “A” represents an input from one or moreaccelerometers, “T” represents an input from a timer, “P” represents acommunications trigger input and “I” represents an image and/or videocapture request input. Thus, in the center portion 376 of the chart, aninput, or combination of inputs, are shown that represent how the device100 detects a transition from a first physical state to a secondphysical state.

As discussed, in the center portion of the chart 376, the inputs thatare received enable the detection of a transition from, for example, aportrait open state to a landscape easel state—shown in bold—“HAT.” Forthis exemplary transition from the portrait open to the landscape easelstate, a Hall Effect sensor (“H”), an accelerometer (“A”) and a timer(“T”) input may be needed. The timer input can be derived from, forexample, a clock associated with the processor.

In addition to the portrait and landscape states, a docked state 368 isalso shown that is triggered based on the receipt of a docking signal372. As discussed above and in relation to FIG. 3, the docking signalcan be triggered by the association of the device 100 with one or moreother device 100 s, accessories, peripherals, smart docks, or the like.

User Interaction:

FIGS. 4A through 4H depict various graphical representations of gestureinputs that may be recognized by the screens 104, 108. The gestures maybe performed not only by a user's body part, such as a digit, but alsoby other devices, such as a stylus, that may be sensed by the contactsensing portion(s) of a screen 104, 108. In general, gestures areinterpreted differently, based on where the gestures are performed(either directly on the display 110, 114 or in the gesture captureregion 120, 124). For example, gestures in the display 110,114 may bedirected to a desktop or application, and gestures in the gesturecapture region 120, 124 may be interpreted as for the system.

With reference to FIGS. 4A-4H, a first type of gesture, a touch gesture420, is substantially stationary on the screen 104,108 for a selectedlength of time. A circle 428 represents a touch or other contact typereceived at particular location of a contact sensing portion of thescreen. The circle 428 may include a border 432, the thickness of whichindicates a length of time that the contact is held substantiallystationary at the contact location. For instance, a tap 420 (or shortpress) has a thinner border 432 a than the border 432 b for a long press424 (or for a normal press). The long press 424 may involve a contactthat remains substantially stationary on the screen for longer timeperiod than that of a tap 420. As will be appreciated, differentlydefined gestures may be registered depending upon the length of timethat the touch remains stationary prior to contact cessation or movementon the screen.

With reference to FIG. 4C, a drag gesture 400 on the screen 104,108 isan initial contact (represented by circle 428) with contact movement 436in a selected direction. The initial contact 428 may remain stationaryon the screen 104,108 for a certain amount of time represented by theborder 432. The drag gesture typically requires the user to contact anicon, window, or other displayed image at a first location followed bymovement of the contact in a drag direction to a new second locationdesired for the selected displayed image. The contact movement need notbe in a straight line but have any path of movement so long as thecontact is substantially continuous from the first to the secondlocations.

With reference to FIG. 4D, a flick gesture 404 on the screen 104,108 isan initial contact (represented by circle 428) with truncated contactmovement 436 (relative to a drag gesture) in a selected direction. Inembodiments, a flick has a higher exit velocity for the last movement inthe gesture compared to the drag gesture. The flick gesture can, forinstance, be a finger snap following initial contact. Compared to a draggesture, a flick gesture generally does not require continual contactwith the screen 104,108 from the first location of a displayed image toa predetermined second location. The contacted displayed image is movedby the flick gesture in the direction of the flick gesture to thepredetermined second location. Although both gestures commonly can movea displayed image from a first location to a second location, thetemporal duration and distance of travel of the contact on the screen isgenerally less for a flick than for a drag gesture.

With reference to FIG. 4E, a pinch gesture 408 on the screen 104,108 isdepicted. The pinch gesture 408 may be initiated by a first contact 428a to the screen 104,108 by, for example, a first digit and a secondcontact 428 b to the screen 104,108 by, for example, a second digit. Thefirst and second contacts 428 a,b may be detected by a common contactsensing portion of a common screen 104,108, by different contact sensingportions of a common screen 104 or 108, or by different contact sensingportions of different screens. The first contact 428 a is held for afirst amount of time, as represented by the border 432 a, and the secondcontact 428 b is held for a second amount of time, as represented by theborder 432 b. The first and second amounts of time are generallysubstantially the same, and the first and second contacts 428 a, bgenerally occur substantially simultaneously. The first and secondcontacts 428 a, b generally also include corresponding first and secondcontact movements 436 a, b, respectively. The first and second contactmovements 436 a, b are generally in opposing directions. Stated anotherway, the first contact movement 436 a is towards the second contact 436b, and the second contact movement 436 b is towards the first contact436 a. More simply stated, the pinch gesture 408 may be accomplished bya user's digits touching the screen 104,108 in a pinching motion.

With reference to FIG. 4F, a spread gesture 410 on the screen 104,108 isdepicted. The spread gesture 410 may be initiated by a first contact 428a to the screen 104,108 by, for example, a first digit and a secondcontact 428 b to the screen 104,108 by, for example, a second digit. Thefirst and second contacts 428 a,b may be detected by a common contactsensing portion of a common screen 104,108, by different contact sensingportions of a common screen 104,108, or by different contact sensingportions of different screens. The first contact 428 a is held for afirst amount of time, as represented by the border 432 a, and the secondcontact 428 b is held for a second amount of time, as represented by theborder 432 b. The first and second amounts of time are generallysubstantially the same, and the first and second contacts 428 a, bgenerally occur substantially simultaneously. The first and secondcontacts 428 a, b generally also include corresponding first and secondcontact movements 436 a, b, respectively. The first and second contactmovements 436 a, b are generally in a common direction. Stated anotherway, the first and second contact movements 436 a, b are away from thefirst and second contacts 428 a, b. More simply stated, the spreadgesture 410 may be accomplished by a user's digits touching the screen104,108 in a spreading motion.

The above gestures may be combined in any manner, such as those shown byFIGS. 4G and 4H, to produce a determined functional result. For example,in FIG. 4G a tap gesture 420 is combined with a drag or flick gesture412 in a direction away from the tap gesture 420. In FIG. 4H, a tapgesture 420 is combined with a drag or flick gesture 412 in a directiontowards the tap gesture 420.

The functional result of receiving a gesture can vary depending on anumber of factors, including a state of the device 100, display 110,114, or screen 104, 108, a context associated with the gesture, orsensed location of the gesture. The state of the device commonly refersto one or more of a configuration of the device 100, a displayorientation, and user and other inputs received by the device 100.Context commonly refers to one or more of the particular application(s)selected by the gesture and the portion(s) of the application currentlyexecuting, whether the application is a single- or multi-screenapplication, and whether the application is a multi-screen applicationdisplaying one or more windows in one or more screens or in one or morestacks. Sensed location of the gesture commonly refers to whether thesensed set(s) of gesture location coordinates are on a touch sensitivedisplay 110, 114 or a gesture capture region 120, 124, whether thesensed set(s) of gesture location coordinates are associated with acommon or different display or screen 104,108, and/or what portion ofthe gesture capture region contains the sensed set(s) of gesturelocation coordinates.

A tap, when received by an a touch sensitive display 110, 114, can beused, for instance, to select an icon to initiate or terminate executionof a corresponding application, to maximize or minimize a window, toreorder windows in a stack, and to provide user input such as bykeyboard display or other displayed image. A drag, when received by atouch sensitive display 110, 114, can be used, for instance, to relocatean icon or window to a desired location within a display, to reorder astack on a display, or to span both displays (such that the selectedwindow occupies a portion of each display simultaneously). A flick, whenreceived by a touch sensitive display 110, 114 or a gesture captureregion 120, 124, can be used to relocate a window from a first displayto a second display or to span both displays (such that the selectedwindow occupies a portion of each display simultaneously). Unlike thedrag gesture, however, the flick gesture is generally not used to movethe displayed image to a specific user-selected location but to adefault location that is not configurable by the user.

The pinch gesture, when received by a touch sensitive display 110, 114or a gesture capture region 120, 124, can be used to minimize orotherwise increase the displayed area or size of a window (typicallywhen received entirely by a common display), to switch windows displayedat the top of the stack on each display to the top of the stack of theother display (typically when received by different displays orscreens), or to display an application manager (a “pop-up window” thatdisplays the windows in the stack). The spread gesture, when received bya touch sensitive display 110, 114 or a gesture capture region 120, 124,can be used to maximize or otherwise decrease the displayed area or sizeof a window, to switch windows displayed at the top of the stack on eachdisplay to the top of the stack of the other display (typically whenreceived by different displays or screens), or to display an applicationmanager (typically when received by an off-screen gesture capture regionon the same or different screens).

The combined gestures of FIG. 4G, when received by a common displaycapture region in a common display or screen 104,108, can be used tohold a first window stack location in a first stack constant for adisplay receiving the gesture while reordering a second window stacklocation in a second window stack to include a window in the displayreceiving the gesture. The combined gestures of FIG. 4H, when receivedby different display capture regions in a common display or screen104,108 or in different displays or screens, can be used to hold a firstwindow stack location in a first window stack constant for a displayreceiving the tap part of the gesture while reordering a second windowstack location in a second window stack to include a window in thedisplay receiving the flick or drag gesture. Although specific gesturesand gesture capture regions in the preceding examples have beenassociated with corresponding sets of functional results, it is to beappreciated that these associations can be redefined in any manner toproduce differing associations between gestures and/or gesture captureregions and/or functional results.

Firmware and Software:

The memory 508 may store and the processor 504 may execute one or moresoftware components. These components can include at least one operatingsystem (OS) 516, an application manager 562, a desktop 566, and/or oneor more applications 564 a and/or 564 b from an application store 560.The OS 516 can include a framework 520, one or more frame buffers 548,one or more drivers 512, previously described in conjunction with FIG.2, and/or a kernel 518. The OS 516 can be any software, consisting ofprograms and data, which manages computer hardware resources andprovides common services for the execution of various applications 564.The OS 516 can be any operating system and, at least in someembodiments, dedicated to mobile devices, including, but not limited to,Linux, ANDROID™, iPhone OS (IOS™), WINDOWS PHONE 7™, etc. The OS 516 isoperable to provide functionality to the phone by executing one or moreoperations, as described herein.

The applications 564 can be any higher level software that executesparticular functionality for the user. Applications 564 can includeprograms such as email clients, web browsers, texting applications,games, media players, office suites, etc. The applications 564 can bestored in an application store 560, which may represent any memory ordata storage, and the management software associated therewith, forstoring the applications 564. Once executed, the applications 564 may berun in a different area of memory 508.

The framework 520 may be any software or data that allows the multipletasks running on the device to interact. In embodiments, at leastportions of the framework 520 and the discrete components describedhereinafter may be considered part of the OS 516 or an application 564.However, these portions will be described as part of the framework 520,but those components are not so limited. The framework 520 can include,but is not limited to, a Multi-Display Management (MDM) module 524, aSurface Cache module 528, a Window Management module 532, an InputManagement module 536, a Task Management module 540, an ApplicationModel Manager 542, a Display Controller, one or more frame buffers 548,a task stack 552, one or more window stacks 550 (which is a logicalarrangement of windows and/or desktops in a display area), and/or anevent buffer 556.

The MDM module 524 includes one or more modules that are operable tomanage the display of applications or other data on the screens of thedevice. An embodiment of the MDM module 524 is described in conjunctionwith FIG. 5B. In embodiments, the MDM module 524 receives inputs fromthe other OS 516 components, such as, the drivers 512, and from theapplications 564 to determine continually the state of the device 100.The inputs assist the MDM module 524 in determining how to configure andallocate the displays according to the application's preferences andrequirements, and the user's actions. Once a determination for displayconfigurations is made, the MDM module 524 can bind the applications 564to a display. The configuration may then be provided to one or moreother components to generate a window with a display.

The Surface Cache module 528 includes any memory or storage and thesoftware associated therewith to store or cache one or more images ofwindows. A series of active and/or non-active windows (or other displayobjects, such as, a desktop display) can be associated with eachdisplay. An active window (or other display object) is currentlydisplayed. A non-active windows (or other display objects) were openedand, at some time, displayed but are now not displayed. To enhance theuser experience, before a window transitions from an active state to aninactive state, a “screen shot” of a last generated image of the window(or other display object) can be stored. The Surface Cache module 528may be operable to store a bitmap of the last active image of a window(or other display object) not currently displayed. Thus, the SurfaceCache module 528 stores the images of non-active windows (or otherdisplay objects) in a data store.

In embodiments, the Window Management module 532 is operable to managethe windows (or other display objects) that are active or not active oneach of the displays. The Window Management module 532, based oninformation from the MDM module 524, the OS 516, or other components,determines when a window (or other display object) is visible or notactive. The Window Management module 532 may then put a non-visiblewindow (or other display object) in a “not active state” and, inconjunction with the Task Management module Task Management 540 suspendsthe application's operation. Further, the Window Management module 532may assign, through collaborative interaction with the MDM module 524, adisplay identifier to the window (or other display object) or manage oneor more other items of data associated with the window (or other displayobject). The Window Management module 532 may also provide the storedinformation to the application 564, the Task Management module 540, orother components interacting with or associated with the window (orother display object). The Window Management module 532 can alsoassociate an input task with a window based on window focus and displaycoordinates within the motion space.

The Input Management module 536 is operable to manage events that occurwith the device. An event is any input into the window environment, forexample, a user interface interactions with a user. The Input Managementmodule 536 receives the events and logically stores the events in anevent buffer 556. Events can include such user interface interactions asa “down event,” which occurs when a screen 104, 108 receives a touchsignal from a user, a “move event,” which occurs when the screen 104,108 determines that a user's finger is moving across a screen(s), an “upevent, which occurs when the screen 104, 108 determines that the userhas stopped touching the screen 104, 108, etc. These events arereceived, stored, and forwarded to other modules by the Input Managementmodule 536. The Input Management module 536 may also map screen inputsto a motion space which is the culmination of all physical and virtualdisplay available on the device.

The motion space is a virtualized space that includes all touchsensitive displays 110,114 “tiled” together to mimic the physicaldimensions of the device 100. For example, when the device 100 isunfolded, the motion space size may be 960×800, which may be the numberof pixels in the combined display area for both touch sensitive displays110, 114. If a user touches on a first touch sensitive display 110 onlocation (40, 40), a full screen window can receive touch event withlocation (40, 40). If a user touches on a second touch sensitive display114, with location (40, 40), the full screen window can receive touchevent with location (520, 40), because the second touch sensitivedisplay 114 is on the right side of the first touch sensitive display110, so the device 100 can offset the touch by the first touch sensitivedisplay's 110 width, which is 480 pixels. When a hardware event occurswith location info from a driver 512, the framework 520 can up-scale thephysical location to the motion space because the location of the eventmay be different based on the device orientation and state. The motionspace may be as described in U.S. patent application Ser. No.13/187,026, filed Jul. 20, 2011, entitled “Systems and Methods forReceiving Gesture Inputs Spanning Multiple Input Devices,” which ishereby incorporated by reference in its entirety for all that it teachesand for all purposes.

A task can be an application and a sub-task can be an applicationcomponent that provides a window with which users can interact to dosomething, such as dial the phone, take a photo, send an email, or viewa map. Each task may be given a window in which to draw a userinterface. The window typically fills a display (for example, touchsensitive display 110,114), but may be smaller than the display 110,114and float on top of other windows. An application usually consists ofmultiple sub-tasks that are loosely bound to each other. Typically, onetask in an application is specified as the “main” task, which ispresented to the user when launching the application for the first time.Each task can then start another task or sub-task to perform differentactions.

The Task Management module 540 is operable to manage the operation ofone or more applications 564 that may be executed by the device. Thus,the Task Management module 540 can receive signals to launch, suspend,terminate, etc. an application or application sub-tasks stored in theapplication store 560. The Task Management module 540 may theninstantiate one or more tasks or sub-tasks of the application 564 tobegin operation of the application 564. Further, the Task ManagementModule 540 may launch, suspend, or terminate a task or sub-task as aresult of user input or as a result of a signal from a collaboratingframework 520 component. The Task Management Module 540 is responsiblefor managing the lifecycle of applications (tasks and sub-task) fromwhen the application is launched to when the application is terminated.

The processing of the Task Management Module 540 is facilitated by atask stack 552, which is a logical structure associated with the TaskManagement Module 540. The task stack 552 maintains the state of alltasks and sub-tasks on the device 100. When some component of theoperating system 516 requires a task or sub-task to transition in itslifecycle, the OS 516 component can notify the Task Management Module540. The Task Management Module 540 may then locate the task orsub-task, using identification information, in the task stack 552, andsend a signal to the task or sub-task indicating what kind of lifecycletransition the task needs to execute. Informing the task or sub-task ofthe transition allows the task or sub-task to prepare for the lifecyclestate transition. The Task Management Module 540 can then execute thestate transition for the task or sub-task. In embodiments, the statetransition may entail triggering the OS kernel 518 to terminate the taskwhen termination is required.

Further, the Task Management module 540 may suspend the application 564based on information from the Window Management Module 532. Suspendingthe application 564 may maintain application data in memory but maylimit or stop the application 564 from rendering a window or userinterface. Once the application becomes active again, the TaskManagement module 540 can again trigger the application to render itsuser interface. In embodiments, if a task is suspended, the task maysave the task's state in case the task is terminated. In the suspendedstate, the application task may not receive input because theapplication window is not visible to the user.

The frame buffer 548 is a logical structure(s) used to render the userinterface. The frame buffer 548 can be created and destroyed by the OSkernel 518. However, the Display Controller 544 can write the imagedata, for the visible windows, into the frame buffer 548. A frame buffer548 can be associated with one screen or multiple screens. Theassociation of a frame buffer 548 with a screen can be controlleddynamically by interaction with the OS kernel 518. A composite displaymay be created by associating multiple screens with a single framebuffer 548. Graphical data used to render an application's window userinterface may then be written to the single frame buffer 548, for thecomposite display, which is output to the multiple screens 104,108. TheDisplay Controller 544 can direct an application's user interface to aportion of the frame buffer 548 that is mapped to a particular display110,114, thus, displaying the user interface on only one screen 104 or108. The Display Controller 544 can extend the control over userinterfaces to multiple applications, controlling the user interfaces foras many displays as are associated with a frame buffer 548 or a portionthereof. This approach compensates for the multiple physical screens104,108 that are in use by the software component above the DisplayController 544.

The Application Manager 562 is an application that provides apresentation layer for the window environment. Thus, the ApplicationManager 562 provides the graphical model for rendering by the TaskManagement Module 540. Likewise, the Desktop 566 provides thepresentation layer for the Application Store 560. Thus, the desktopprovides a graphical model of a surface having selectable applicationicons for the Applications 564 in the Application Store 560 that can beprovided to the Window Management Module 556 for rendering.

Further, the framework can include an Application Model Manager (AMM)542. The Application Manager 562 may interface with the AMM 542. Inembodiments, the AMM 542 receives state change information from thedevice 100 regarding the state of applications (which are running orsuspended). The AMM 542 can associate bit map images from the SurfaceCache Module 528 to the tasks that are alive (running or suspended).Further, the AMM 542 can convert the logical window stack maintained inthe Task Manager Module 540 to a linear (“film strip” or “deck ofcards”) organization that the user perceives when the using the offgesture capture area 120 to sort through the windows. Further, the AMM542 may provide a list of executing applications to the ApplicationManager 562.

An embodiment of the MDM module 524 is shown in FIG. 5B. The MDM module524 is operable to determine the state of the environment for thedevice, including, but not limited to, the orientation of the device,whether the device 100 is opened or closed, what applications 564 areexecuting, how the applications 564 are to be displayed, what actionsthe user is conducting, the tasks being displayed, etc. To configure thedisplay, the MDM module 524 interprets these environmental factors anddetermines a display configuration, as described in conjunction withFIGS. 6A-6J. Then, the MDM module 524 can bind the applications 564 orother device components to the displays. The configuration may then besent to the Display Controller 544 and/or the other components withinthe OS 516 to generate the display. The MDM module 524 can include oneor more of, but is not limited to, a Display Configuration Module 568, aPreferences Module 572, a Device State Module 574, a Gesture Module 576,a Requirements Module 580, an Event Module 584, and/or a Binding Module588.

The Display Configuration Module 568 determines the layout for thedisplay. In embodiments, the Display Configuration Module 568 candetermine the environmental factors. The environmental factors may bereceived from one or more other MDM modules 524 or from other sources.The Display Configuration Module 568 can then determine from the list offactors the best configuration for the display. Some embodiments of thepossible configurations and the factors associated therewith aredescribed in conjunction with FIGS. 6A-6F.

The Preferences Module 572 is operable to determine display preferencesfor an application 564 or other component. For example, an applicationcan have a preference for Single or Dual displays. The PreferencesModule 572 can determine an application's display preference (e.g., byinspecting the application's preference settings) and may allow theapplication 564 to change to a mode (e.g., single screen, dual screen,max, etc.) if the device 100 is in a state that can accommodate thepreferred mode. However, some user interface policies may disallow amode even if the mode is available. As the configuration of the devicechanges, the preferences may be reviewed to determine if a betterdisplay configuration can be achieved for an application 564.

The Device State Module 574 is operable to determine or receive thestate of the device. The state of the device can be as described inconjunction with FIGS. 3A and 3B. The state of the device can be used bythe Display Configuration Module 568 to determine the configuration forthe display. As such, the Device State Module 574 may receive inputs andinterpret the state of the device. The state information is thenprovided to the Display Configuration Module 568.

The Gesture Module 576 is shown as part of the MDM module 524, but, inembodiments, the Gesture module 576 may be a separate Framework 520component that is separate from the MDM module 524. In embodiments, theGesture Module 576 is operable to determine if the user is conductingany actions on any part of the user interface. In alternativeembodiments, the Gesture Module 576 receives user interface actions fromthe configurable area 112,116 only. The Gesture Module 576 can receivetouch events that occur on the configurable area 112,116 (or possiblyother user interface areas) by way of the Input Management Module 536and may interpret the touch events (using direction, speed, distance,duration, and various other parameters) to determine what kind ofgesture the user is performing. When a gesture is interpreted, theGesture Module 576 can initiate the processing of the gesture and, bycollaborating with other Framework 520 components, can manage therequired window animation. The Gesture Module 576 collaborates with theApplication Model Manager 542 to collect state information with respectto which applications are running (active or paused) and the order inwhich applications must appear when a user gesture is performed. TheGesture Module 576 may also receive references to bitmaps (from theSurface Cache Module 528) and live windows so that when a gesture occursit can instruct the Display Controller 544 how to move the window(s)across the display 110,114. Thus, suspended applications may appear tobe running when those windows are moved across the display 110,114.

Further, the Gesture Module 576 can receive task information either fromthe Task Manage Module 540 or the Input Management module 536. Thegestures may be as defined in conjunction with FIGS. 4A through 4H. Forexample, moving a window causes the display to render a series ofdisplay frames that illustrate the window moving. The gesture associatedwith such user interface interaction can be received and interpreted bythe Gesture Module 576. The information about the user gesture is thensent to the Task Management Module 540 to modify the display binding ofthe task.

The Requirements Module 580, similar to the Preferences Module 572, isoperable to determine display requirements for an application 564 orother component. An application can have a set display requirement thatmust be observed. Some applications require a particular displayorientation. For example, the application “Angry Birds” can only bedisplayed in landscape orientation. This type of display requirement canbe determined or received, by the Requirements Module 580. As theorientation of the device changes, the Requirements Module 580 canreassert the display requirements for the application 564. The DisplayConfiguration Module 568 can generate a display configuration that is inaccordance with the application display requirements, as provided by theRequirements Module 580.

The Event Module 584, similar to the Gesture Module 576, is operable todetermine one or more events occurring with an application or othercomponent that can affect the user interface. Thus, the Event Module 584can receive event information either from the event buffer 556 or theTask Management module 540. These events can change how the tasks arebound to the displays. The Event Module 584 can collect state changeinformation from other Framework 520 components and act upon that statechange information. In an example, when the phone is opened or closed orwhen an orientation change has occurred, a new message may be renderedin a secondary screen. The state change based on the event can bereceived and interpreted by the Event Module 584. The information aboutthe events then may be sent to the Display Configuration Module 568 tomodify the configuration of the display.

The Binding Module 588 is operable to bind the applications 564 or theother components to the configuration determined by the DisplayConfiguration Module 568. A binding associates, in memory, the displayconfiguration for each application with the display and mode of theapplication. Thus, the Binding Module 588 can associate an applicationwith a display configuration for the application (e.g. landscape,portrait, multi-screen, etc.). Then, the Binding Module 588 may assign adisplay identifier to the display. The display identifier associated theapplication with a particular display of the device 100. This binding isthen stored and provided to the Display Controller 544, the othercomponents of the OS 516, or other components to properly render thedisplay. The binding is dynamic and can change or be updated based onconfiguration changes associated with events, gestures, state changes,application preferences or requirements, etc.

User Interface Configurations:

With reference now to FIGS. 6A-J, various types of output configurationsmade possible by the device 100 will be described hereinafter.

FIGS. 6A and 6B depict two different output configurations of the device100 being in a first state. Specifically, FIG. 6A depicts the device 100being in a closed portrait state 304 where the data is displayed on theprimary screen 104. In this example, the device 100 displays data viathe touch sensitive display 110 in a first portrait configuration 604.As can be appreciated, the first portrait configuration 604 may onlydisplay a desktop or operating system home screen. Alternatively, one ormore windows may be presented in a portrait orientation while the device100 is displaying data in the first portrait configuration 604.

FIG. 6B depicts the device 100 still being in the closed portrait state304, but instead data is displayed on the secondary screen 108. In thisexample, the device 100 displays data via the touch sensitive display114 in a second portrait configuration 608.

It may be possible to display similar or different data in either thefirst or second portrait configuration 604, 608. It may also be possibleto transition between the first portrait configuration 604 and secondportrait configuration 608 by providing the device 100 a user gesture(e.g., a double tap gesture), a menu selection, or other means. Othersuitable gestures may also be employed to transition betweenconfigurations. Furthermore, it may also be possible to transition thedevice 100 from the first or second portrait configuration 604, 608 toany other configuration described herein depending upon which state thedevice 100 is moved.

An alternative output configuration may be accommodated by the device100 being in a second state. Specifically, FIG. 6C depicts a thirdportrait configuration where data is displayed simultaneously on boththe primary screen 104 and the secondary screen 108. The third portraitconfiguration may be referred to as a Dual-Portrait (PD) outputconfiguration. In the PD output configuration, the touch sensitivedisplay 110 of the primary screen 104 depicts data in the first portraitconfiguration 604 while the touch sensitive display 114 of the secondaryscreen 108 depicts data in the second portrait configuration 608. Thesimultaneous presentation of the first portrait configuration 604 andthe second portrait configuration 608 may occur when the device 100 isin an open portrait state 320. In this configuration, the device 100 maydisplay one application window in one display 110 or 114, twoapplication windows (one in each display 110 and 114), one applicationwindow and one desktop, or one desktop. Other configurations may bepossible. It should be appreciated that it may also be possible totransition the device 100 from the simultaneous display ofconfigurations 604, 608 to any other configuration described hereindepending upon which state the device 100 is moved. Furthermore, whilein this state, an application's display preference may place the deviceinto bilateral mode, in which both displays are active to displaydifferent windows in the same application. For example, a Cameraapplication may display a viewfinder and controls on one side, while theother side displays a mirrored preview that can be seen by the photosubjects. Games involving simultaneous play by two players may also takeadvantage of bilateral mode.

FIGS. 6D and 6E depicts two further output configurations of the device100 being in a third state. Specifically, FIG. 6D depicts the device 100being in a closed landscape state 340 where the data is displayed on theprimary screen 104. In this example, the device 100 displays data viathe touch sensitive display 110 in a first landscape configuration 612.Much like the other configurations described herein, the first landscapeconfiguration 612 may display a desktop, a home screen, one or morewindows displaying application data, or the like.

FIG. 6E depicts the device 100 still being in the closed landscape state340, but instead data is displayed on the secondary screen 108. In thisexample, the device 100 displays data via the touch sensitive display114 in a second landscape configuration 616. It may be possible todisplay similar or different data in either the first or second portraitconfiguration 612, 616. It may also be possible to transition betweenthe first landscape configuration 612 and second landscape configuration616 by providing the device 100 with one or both of a twist and tapgesture or a flip and slide gesture. Other suitable gestures may also beemployed to transition between configurations. Furthermore, it may alsobe possible to transition the device 100 from the first or secondlandscape configuration 612, 616 to any other configuration describedherein depending upon which state the device 100 is moved.

FIG. 6F depicts a third landscape configuration where data is displayedsimultaneously on both the primary screen 104 and the secondary screen108. The third landscape configuration may be referred to as aDual-Landscape (LD) output configuration. In the LD outputconfiguration, the touch sensitive display 110 of the primary screen 104depicts data in the first landscape configuration 612 while the touchsensitive display 114 of the secondary screen 108 depicts data in thesecond landscape configuration 616. The simultaneous presentation of thefirst landscape configuration 612 and the second landscape configuration616 may occur when the device 100 is in an open landscape state 340. Itshould be appreciated that it may also be possible to transition thedevice 100 from the simultaneous display of configurations 612, 616 toany other configuration described herein depending upon which state thedevice 100 is moved.

FIGS. 6G and 6H depict two views of a device 100 being in yet anotherstate. Specifically, the device 100 is depicted as being in an easelstate 312. FIG. 6G shows that a first easel output configuration 618 maybe displayed on the touch sensitive display 110. FIG. 6H shows that asecond easel output configuration 620 may be displayed on the touchsensitive display 114. The device 100 may be configured to depict eitherthe first easel output configuration 618 or the second easel outputconfiguration 620 individually. Alternatively, both the easel outputconfigurations 618, 620 may be presented simultaneously. In someembodiments, the easel output configurations 618, 620 may be similar oridentical to the landscape output configurations 612, 616. The device100 may also be configured to display one or both of the easel outputconfigurations 618, 620 while in a modified easel state 316. It shouldbe appreciated that simultaneous utilization of the easel outputconfigurations 618, 620 may facilitate two-person games (e.g.,Battleship®, chess, checkers, etc.), multi-user conferences where two ormore users share the same device 100, and other applications. As can beappreciated, it may also be possible to transition the device 100 fromthe display of one or both configurations 618, 620 to any otherconfiguration described herein depending upon which state the device 100is moved.

FIG. 6I depicts yet another output configuration that may beaccommodated while the device 100 is in an open portrait state 320.Specifically, the device 100 may be configured to present a singlecontinuous image across both touch sensitive displays 110, 114 in aportrait configuration referred to herein as a Portrait-Max (PMax)configuration 624. In this configuration, data (e.g., a single image,application, window, icon, video, etc.) may be split and displayedpartially on one of the touch sensitive displays while the other portionof the data is displayed on the other touch sensitive display. The Pmaxconfiguration 624 may facilitate a larger display and/or betterresolution for displaying a particular image on the device 100. Similarto other output configurations, it may be possible to transition thedevice 100 from the Pmax configuration 624 to any other outputconfiguration described herein depending upon which state the device 100is moved.

FIG. 6J depicts still another output configuration that may beaccommodated while the device 100 is in an open landscape state 348.Specifically, the device 100 may be configured to present a singlecontinuous image across both touch sensitive displays 110, 114 in alandscape configuration referred to herein as a Landscape-Max (LMax)configuration 628. In this configuration, data (e.g., a single image,application, window, icon, video, etc.) may be split and displayedpartially on one of the touch sensitive displays while the other portionof the data is displayed on the other touch sensitive display. The Lmaxconfiguration 628 may facilitate a larger display and/or betterresolution for displaying a particular image on the device 100. Similarto other output configurations, it may be possible to transition thedevice 100 from the Lmax configuration 628 to any other outputconfiguration described herein depending upon which state the device 100is moved.

The device 100 manages desktops and/or windows with at least one windowstack 700, 728, as shown in FIGS. 7A and 7B. A window stack 700, 728 isa logical arrangement of active and/or inactive windows for amulti-screen device. For example, the window stack 700, 728 may belogically similar to a deck of cards, where one or more windows ordesktops are arranged in order, as shown in FIGS. 7A and 7B. An activewindow is a window that is currently being displayed on at least one ofthe touch sensitive displays 110, 114. For example, windows 104 and 108are active windows and are displayed on touch sensitive displays 110 and114. An inactive window is a window that was opened and displayed but isnow “behind” an active window and not being displayed. In embodiments,an inactive window may be for an application that is suspended, andthus, the window is not displaying active content. For example, windows712, 716, 720, and 724 are inactive windows.

A window stack 700, 728 may have various arrangements or organizationalstructures. In the embodiment shown in FIG. 7A, the device 100 includesa first stack 760 associated with a first touch sensitive display 110and a second stack associated with a second touch sensitive display 114.Thus, each touch sensitive display 110, 114 can have an associatedwindow stack 760, 764. These two window stacks 760, 764 may havedifferent numbers of windows arranged in the respective stacks 760, 764.Further, the two window stacks 760, 764 can also be identifieddifferently and managed separately. Thus, the first window stack 760 canbe arranged in order from a first window 704 to a next window 720 to alast window 724 and finally to a desktop 722, which, in embodiments, isat the “bottom” of the window stack 760. In embodiments, the desktop 722is not always at the “bottom” as application windows can be arranged inthe window stack below the desktop 722, and the desktop 722 can bebrought to the “top” of a stack over other windows during a desktopreveal. Likewise, the second stack 764 can be arranged from a firstwindow 708 to a next window 712 to a last window 716, and finally to adesktop 718, which, in embodiments, is a single desktop area, withdesktop 722, under all the windows in both window stack 760 and windowstack 764. A logical data structure for managing the two window stacks760, 764 may be as described in conjunction with FIG. 8.

Another arrangement for a window stack 728 is shown in FIG. 7B. In thisembodiment, there is a single window stack 728 for both touch sensitivedisplays 110, 114. Thus, the window stack 728 is arranged from a desktop758 to a first window 744 to a last window 756. A window can be arrangedin a position among all windows without an association to a specifictouch sensitive display 110, 114. In this embodiment, a window is in theorder of windows. Further, at least one window is identified as beingactive. For example, a single window may be rendered in two portions 732and 736 that are displayed on the first touch sensitive screen 110 andthe second touch sensitive screen 114. The single window may only occupya single position in the window stack 728 although it is displayed onboth displays 110, 114.

Yet another arrangement of a window stack 760 is shown in FIGS. 7Cthrough 7E. The window stack 760 is shown in three “elevation” views. InFIG. 7C, the top of the window stack 760 is shown. Two sides of thewindow stack 760 are shown in FIGS. 7D and 7E. In this embodiment, thewindow stack 760 resembles a stack of bricks. The windows are stacked oneach other. Looking from the top of the window stack 760 in FIG. 7C,only the top most windows in the window stack 760 are seen in differentportions of the composite display 764. The composite display 764represents a logical model for the entire display area of the device100, which can include touch sensitive display 110 and touch sensitivedisplay 114. A desktop 786 or a window can occupy part or all of thecomposite display 764.

In the embodiment shown, the desktop 786 is the lowest display or“brick” in the window stack 760. Thereupon, window 1 782, window 2 782,window 3 768, and window 4 770 are layered. Window 1 782, window 3 768,window 2 782, and window 4 770 only occupy a portion of the compositedisplay 764. Thus, another part of the stack 760 includes window 8 774and windows 5 through 7 shown in section 790. Only the top window in anyportion of the composite display 764 is actually rendered and displayed.Thus, as shown in the top view in FIG. 7C, window 4 770, window 8 774,and window 3 768 are displayed as being at the top of the display indifferent portions of the window stack 760. A window can be dimensionedto occupy only a portion of the composite display 760 to “reveal”windows lower in the window stack 760. For example, window 3 768 islower in the stack than both window 4 770 and window 8 774 but is stilldisplayed. A logical data structure to manage the window stack can be asdescribed in conjunction with FIG. 8.

When a new window is opened, the newly activated window is generallypositioned at the top of the stack. However, where and how the window ispositioned within the stack can be a function of the orientation of thedevice 100, the context of what programs, functions, software, etc. arebeing executed on the device 100, how the stack is positioned when thenew window is opened, etc. To insert the window in the stack, theposition in the stack for the window is determined and the touchsensitive display 110, 114 to which the window is associated may also bedetermined. With this information, a logical data structure for thewindow can be created and stored. When user interface or other events ortasks change the arrangement of windows, the window stack(s) can bechanged to reflect the change in arrangement. It should be noted thatthese same concepts described above can be used to manage the one ormore desktops for the device 100.

A logical data structure 800 for managing the arrangement of windows ordesktops in a window stack is shown in FIG. 8. The logical datastructure 800 can be any data structure used to store data whether anobject, record, file, etc. The logical data structure 800 can be storedin any type of database or data storage system, regardless of protocolor standard. In embodiments, the logical data structure 800 includes oneor more portions, fields, attributes, etc. that store data in a logicalarrangement that allows for easy storage and retrieval of theinformation. Hereinafter, these one or more portions, fields,attributes, etc. shall be described simply as fields. The fields canstore data for a window identifier 804, dimensions 808, a stack positionidentifier 812, a display identifier 816, and/or an active indicator820. Each window in a window stack can have an associated logical datastructure 800. While only a single logical data structure 800 is shownin FIG. 8, there may be more or fewer logical data structures 800 usedwith a window stack (based on the number of windows or desktops in thestack), as represented by ellipses 824. Further, there may be more orfewer fields than those shown in FIG. 8, as represented by ellipses 828.

A window identifier 804 can include any identifier (ID) that uniquelyidentifies the associated window in relation to other windows in thewindow stack. The window identifier 804 can be a globally uniqueidentifier (GUID), a numeric ID, an alphanumeric ID, or other type ofidentifier. In embodiments, the window identifier 804 can be one, two,or any number of digits based on the number of windows that can beopened. In alternative embodiments, the size of the window identifier804 may change based on the number of windows opened. While the windowis open, the window identifier 804 may be static and remain unchanged.

Dimensions 808 can include dimensions for a window in the compositedisplay 760. For example, the dimensions 808 can include coordinates fortwo or more corners of the window or may include one coordinate anddimensions for the width and height of the window. These dimensions 808can delineate what portion of the composite display 760 the window mayoccupy, which may the entire composite display 760 or only part ofcomposite display 760. For example, window 4 770 may have dimensions 880that indicate that the window 770 will occupy only part of the displayarea for composite display 760, as shown in FIGS. 7 c through 7E. Aswindows are moved or inserted in the window stack, the dimensions 808may change.

A stack position identifier 812 can be any identifier that can identifythe position in the stack for the window or may be inferred from thewindow's control record within a data structure, such as a list or astack. The stack position identifier 812 can be a GUID, a numeric ID, analphanumeric ID, or other type of identifier. Each window or desktop caninclude a stack position identifier 812. For example, as shown in FIG.7A, window 1 704 in stack 1 760 can have a stack position identifier 812of 1 identifying that window 704 is the first window in the stack 760and the active window. Similarly, window 6 724 can have a stack positionidentifier 812 of 3 representing that window 724 is the third window inthe stack 760. Window 2 708 can also have a stack position identifier812 of 1 representing that window 708 is the first window in the secondstack 764. As shown in FIG. 7B, window 1 744 can have a stack positionidentifier 812 of 1, window 3, rendered in portions 732 and 736, canhave a stack position identifier 812 of 3, and window 6 756 can have astack position identifier 812 of 6. Thus, depending on the type ofstack, the stack position identifier 812 can represent a window'slocation in the stack.

A display identifier 816 can identify that the window or desktop isassociated with a particular display, such as the first display 110 orthe second display 114, or the composite display 760 composed of bothdisplays. While this display identifier 816 may not be needed for amulti-stack system, as shown in FIG. 7A, the display identifier 816 canindicate whether a window in the serial stack of FIG. 7B is displayed ona particular display. Thus, window 3 may have two portions 732 and 736in FIG. 7B. The first portion 732 may have a display identifier 816 forthe first display while the second portion 736 may have a displayidentifier 816 for the second display 114. However, in alternativeembodiments, the window may have two display identifier 816 thatrepresent that the window is displayed on both of the displays 110, 114,or a display identifier 816 identifying the composite display. Inanother alternate embodiment, the window may have a single displayidentifier 816 to represent that the window is displayed on both of thedisplays 110, 114.

Similar to the display identifier 816, an active indicator 820 may notbe needed with the dual stack system of FIG. 7A, as the window in stackposition 1 is active and displayed. In the system of FIG. 7B, the activeindicator 820 can indicate which window(s) in the stack is beingdisplayed. Thus, window 3 may have two portions 732 and 736 in FIG. 7.The first portion 732 may have an active indicator 820 while the secondportion 736 may also have an active indicator 820. However, inalternative embodiments, window 3 may have a single active indicator820. The active indicator 820 can be a simple flag or bit thatrepresents that the window is active or displayed.

An embodiment of a method 900 for creating a window stack is shown inFIG. 9. While a general order for the steps of the method 900 is shownin FIG. 9. Generally, the method 900 starts with a start operation 904and ends with an end operation 928. The method 900 can include more orfewer steps or can arrange the order of the steps differently than thoseshown in FIG. 9. The method 900 can be executed as a set ofcomputer-executable instructions executed by a computer system andencoded or stored on a computer readable medium. Hereinafter, the method900 shall be explained with reference to the systems, components,modules, software, data structures, user interfaces, etc. described inconjunction with FIGS. 1-8.

A multi-screen device 100 can receive activation of a window, in step908. In embodiments, the multi-screen device 100 can receive activationof a window by receiving an input from the touch sensitive display 110or 114, the configurable area 112 or 116, a gesture capture region 120or 124, or some other hardware sensor operable to receive user interfaceinputs. The processor may execute the Task Management Module 540 mayreceive the input. The Task Management Module 540 can interpret theinput as requesting an application task to be executed that will open awindow in the window stack.

In embodiments, the Task Management Module 540 places the user interfaceinteraction in the task stack 552 to be acted upon by the DisplayConfiguration Module 568 of the Multi-Display Management Module 524.Further, the Task Management Module 540 waits for information from theMulti-Display Management Module 524 to send instructions to the WindowManagement Module 532 to create the window in the window stack.

The Multi-Display Management Module 524, upon receiving instruction fromthe Task Management Module 540, determines to which touch portion of thecomposite display 760, the newly activated window should be associated,in step 912. For example, window 4 770 is associated with the a portionof the composite display 764 In embodiments, the device state module 574of the Multi-Display Management Module 524 may determine how the deviceis oriented or in what state the device is in, e.g., open, closed,portrait, etc. Further, the preferences module 572 and/or requirementsmodule 580 may determine how the window is to be displayed. The gesturemodule 576 may determine the user's intentions about how the window isto be opened based on the type of gesture and the location of where thegesture is made.

The Display Configuration Module 568 may use the input from thesemodules and evaluate the current window stack 760 to determine the bestplace and the best dimensions, based on a visibility algorithm, to openthe window. Thus, the Display Configuration Module 568 determines thebest place to put the window at the top of the window stack 760, in step916. The visibility algorithm, in embodiments, determines for allportions of the composite display, which windows are at the top of thestack. For example, the visibility algorithm determines that window 3768, window 4 770, and window 8 774 are at the top of the stack 760 asviewed in FIGS. 7C through 7E. Upon determining where to open thewindow, the Display Configuration Module 568 can assign a displayidentifier 816 and possibly dimensions 808 to the window. The displayidentifier 816 and dimensions 808 can then be sent back to the TaskManagement Module 540. The Task Management Module 540 may then assignthe window a stack position identifier 812 indicating the windowsposition at the top of the window stack.

In embodiments, the Task Management Module 540 sends the window stackinformation and instructions to render the window to the WindowManagement Module 532. The Window Management Module 532 and the TaskManagement Module 540 can create the logical data structure 800, in step924. Both the Task Management Module 540 and the Window ManagementModule 532 may create and manage copies of the window stack. Thesecopies of the window stack can be synchronized or kept similar throughcommunications between the Window Management Module 532 and the TaskManagement Module 540. Thus, the Window Management Module 532 and theTask Management Module 540, based on the information determined by theMulti-Display Management Module 524, can assign dimensions 808, a stackposition identifier 812 (e.g., window 1 782, window 4 770, etc.), adisplay identifier 816 (e.g., touch sensitive display 1 110, touchsensitive display 2 114, composite display identifier, etc,), and anactive indicator 820, which is generally always set when the window isat the “top” of the stack. The logical data structure 800 may then bestored by both the Window Management Module 532 and the Task ManagementModule 540. Further, the Window Management Module 532 and the TaskManagement Module 540 may thereinafter manage the window stack and thelogical data structure(s) 800.

Demand for portable electronic devices with high levels of functionalitycontinues to rise and personal electronic devices continue to becomeincreasingly more portable. While computer power, battery life, screensize and overall functionality of portable phones and smart phonescontinues to increase, user reliance on these devices increases. Manyusers of such devices rely heavily on such devices for generalcommunication, accessing the internet, cloud computing, and accessingvarious locally stored information such as contact information, files,music, pictures and the like. It is often desirable therefore to connectsuch heavily relied on devices to an additional computing device ordisplay, such as a monitor or tablet device, such as a smartpad (SP)1000 (see FIG. 10).

Accordingly, it is desirable for the device 100 to be able to interfacewith an additional device, such as the smartpad 1000, that enablesfunctionality similar to, for example, both a tablet computer system andsmart phone. Furthermore, a need exists for the above-described deviceto allow for various pre-existing features of both devices, such assending and receiving phone calls and further allowing for theaccessibility of applications running on the device 100. A need alsoexists for the above device 100 to provide the benefits of both a tabletcomputer system and cellular phone in one integrative device by allowingfor common operations and functionality without compromising the formfactor of the device.

One exemplary embodiment is directed toward a selectively removabledevice and smartpad system. The smartpad system is discussed in greaterdetail hereinafter, and can have various features for complementing thecommunications device, such as a smart phone or device 100. For example,the smartpad may supplement the device 100 by providing increased screensize, increased processor size, increased battery or power supply, orthe like. Similarly, the device 100 may compliment the SP 1000 byproviding connectivity through one or more wireless networks, access tovarious stored information, and the like. It will expressly recognizedtherefore that two or more devices of the present invention may beprovided in a connected or docked and generally symbiotic relationship.It will further be recognized that the devices provide various features,benefits and functionality in their independent state(s).

In accordance with one exemplary embodiment, the device 100 is capableof being received by the SP 1000 through a recessed feature of the SP1000 having corresponding dimensions to the device 100. In one exemplaryembodiment, the SP 1000 is provided and preferably sized for receiving apredetermined device 100. In alternative embodiments, however, it iscontemplated that the SP 1000 is provided, the smartpad capable ofreceiving a plurality of communications devices of different sizes. Insuch embodiments, the SP 1000 may receive communications devices ofvarious sizes by, for example, the inclusion of additional elements,such as spacers and various adjustable features.

In accordance with one exemplary embodiment, the device 100 and SP 1000have a docking relationship that is established when the device 100 isconnected to the SP 1000 during various modes of operation. For example,in one embodiment, a system is provided comprising the SP 1000 and thedevice 100, the SP 1000 capable of physically receiving the device 100,wherein the device 100 is operable as the primary computing device. Insuch an embodiment, the SP 1000 may, for example, simply provideenhanced audio and visual features for the device 100 that comprises itsown CPU, memory, and the like. It is further contemplated that thesystem can be placed in a mode of operation wherein the device 100docked to the SP 1000 provide it in a more passive mode where, forexample, the device 100 draws power from the SP 1000 such as to rechargea battery of the device 100.

In accordance with another exemplary embodiment, the device 100 and SP1000 are provided wherein the device 100 is received or docked with theSP 1000 and wherein a substantial area of the device 100 is positionedwithin one or more compartments of the SP 1000. For example, where asvarious known devices comprise docking features which require or resultin the docked item to be generally exposed, thereby substantiallyaltering the external dimensions of the host device and/or creating apotential for damaging one or both devices upon impact, an exemplaryembodiment contemplates the SP 1000 which receives the device 100 in amanner such that the external dimensions of the SP 1000 are notsubstantially altered when the devices are connected. In such anarrangement, the device 100 and associated connection means aregenerally protected and the SP 1000 is allowed to substantially maintainits original shape. In accordance with one exemplary embodiment, the SP1000 is capable of receiving and/or docking the device 100 wherein thedevice 100 is received in lockable association with the SP 1000. As usedherein, the term “lockable” is not intended to designate or limit it toany particular arrangement. Rather, lockable is intended to refer tovarious embodiments as described herein and will be recognized by one ofordinary skill in the art. In one embodiment, the device 100 isconnectable to the SP 1000 wherein the SP 1000 comprises extensionsprings for first electively securing the device 100 in a docked mannerand an ejection feature for releasing the device 100 from the SP 1000.Moreover, as will be described in greater detail below, it should beappreciated that the device 100 and SP 1000 can communicate using wiredand/or wireless technology(ies) with equal success. Moreover, and inaccordance with another exemplary embodiment, the hinged device 100 isselectively connectable to the SP 1000 wherein the device 100 isreceived by the SP 1000 in an open position and where in one or morepreexisting ports of the SP 1000 correspond with internal receivingfeatures of the SP 1000, such that the device 100 and the SP 1000 may beoperated simultaneously in various modes of use.

In accordance with some exemplary embodiments, the SP 1000 is providedwith an eject or release button to facilitate the removal of a stored ordocked device 100.

FIG. 10 illustrates an exemplary smartpad (SP) 1000 according to anexemplary embodiment. The exemplary smartpad at least provides a largertouch sensitive display operatively coupleable to device 100.

While the following description uses the term “smart” in conjunctionwith the display device 1000, it is to be appreciated that this termdoes not necessarily connotate that there is intelligence in thesmartpad. Rather, it is to be appreciated that there can be“intelligence,” including one or more of a processor(s), memory,storage, display drivers, etc., in the smartpad, and/or one or more ofthese elements shared with the device 100 via, for example, one or moreof a port, bus, connection, or the like. In general, any one or more ofthe functions of the device 100 is extendable to the smartpad 700 andvice versa.

The exemplary smartpad 700 includes a screen 1004, a SP touch sensitivedisplay 1010, a SP configurable area 1008, a SP gesture captureregion(s) 1012 and a SP camera 1016. The SP 1000 also includes a port(not visible in this orientation) adapted to receive the device 100 asillustrated at least in FIG. 11.

The device 100 docks with the smartpad 1000 via the port on the SP 1000and the corresponding port 136 on device 100. As discussed, port 136 insome embodiments is an input/output port (I/O port) that allows thedevice 100 to be connected to other peripheral devices, such as adisplay, keyboard, printing device and/or SP 1000. In accordance withone exemplary embodiment, the docking is accomplished by the device 100sliding into the left-hand side of the SP 1000, with the device 100being in an open state and the device 100 engaging a port in the SP 1000corresponding to port 136. In accordance with one exemplary embodiment,the device 100 engages a doored cassette-like slot in the SP 1000 intowhich the device 100 slides. (See for example FIG. 13) It should beappreciated however that there may be other configurations forphysically and electrically engaging the two devices—in general, themanner of engagement is not important provided the device 100 and SP1000 are in electrical communication with one another.

The SP 1000 includes a screen 1004. In some embodiments, the entirefront surface of the SP 1000 may be touch sensitive and capable ofreceiving input by a user touching the front surface of the screen 1004.The screen 1004 includes touch sensitive display 1010, which, inaddition to being touch sensitive, is also capable of displayinginformation to a user.

The screen 1004 also includes a configurable area 1008 that has beenconfigured for specific inputs when the user touches portions of theconfigurable area 1008. Area 1012 a is configured to receive a “back”input indicating that a user would like to view information previouslydisplayed. Area 1012 b is configured to receive a “menu” inputindicating that the user would like to view options from a menu. Area1012 c is configured to receive a “home” input indicating that the userwould like to view information associated with a “home” view.

In other embodiments, areas 1012 a-c may be configured, in addition tothe configurations described above, for other types of specific inputsincluding controlling features of device 100 and/or device 1000, somenon-limiting examples including adjusting overall system power,adjusting the volume, adjusting the brightness, adjusting the vibration,selecting of displayed items on screen 1004, operating the SP camera1016, operating a microphone, and initiating/terminating of telephonecalls. Also, in some embodiments, areas 1012 a-c may be configured forspecific inputs depending upon the application running on device 100/SP1000 and/or information displayed on the touch sensitive displays 1010.

In addition to touch sensing, screen 1004 may also include areas thatreceive input from a user without requiring the user to touch thedisplay area of the screen. For example, screen 1004 can include gesturecapture area 1012. These areas are able to receive input by recognizinggestures made by a user without the need for the user to actually touchthe surface of the display area. In comparison to touch sensitivedisplay 1010 and 1014, the gesture capture area 1012 may not be capableof rendering a displayed image.

While not illustrated, there may also be a number of hardware componentswithin SP 1000. As illustrated in FIG. 10, SP 1000 can include aspeaker, a microphone and one or more cameras 1016. Upon docking thedevice 100 in the SP 1000, the corresponding device(s) (e.g., thespeaker) in the device 100 could be disabled in favor of the speaker inthe SP 1000. Similarly, other components, such as the screen 1004,microphone, speaker, etc, could be disabled on the device 100 in favorof the SP 1000.

In general, the touch sensitive display 1010 may comprise a full color,touch sensitive display. A second area within each touch sensitivescreen 1004 may comprise the SP gesture capture region 1012. The SPgesture capture region 1012 may comprise an area or region that isoutside of the SP touch sensitive display 1010 area that is capable ofreceiving input, for example in the form of gestures provided by a user.However, the SP gesture capture region 1012 does not necessarily includepixels that can perform a display function or capability.

A third region of the SP touch sensitive screen 1004 may comprise theconfigurable area 1012. The configurable area 1012 is capable ofreceiving input and has display or limited display capabilities. Inembodiments, the configurable area 1012 may present different inputoptions to the user. For example, the configurable area 1012 may displaybuttons or other relatable items. Moreover, the identity of displayedbuttons, or whether any buttons are displayed at all within theconfigurable area 1012 of the SP touch sensitive screen 1004 may bedetermined from the context in which the device 1000 is used and/oroperated. In an exemplary embodiment, the touch sensitive screen 1004comprise liquid crystal display devices extending across at least thoseregions of the touch sensitive screen 1004 that is capable of providingvisual output to a user, and a capacitive input matrix over thoseregions of the touch sensitive screen 1004 that is capable of receivinginput from the user.

As discussed above with reference to FIGS. 4A through 4H, the variousgraphical representations of gesture inputs that may be recognized bythe screens 104, 108 are also recognizable by screen 1004. As discussed,the gestures may be performed not only by a user's body part, such as adigit, but also by other devices, such as a stylus, that may be sensedby the contact sensing portion(s) of a screen 1004. In general, gesturesare interpreted differently, based on where the gestures are performed(either directly on the display 1004 or in the gesture capture region1020). For example, gestures in the display 1010 may be directed to adesktop or application, and gestures in the gesture capture region 1020may be interpreted as for the system.

In addition to the above, the SP touch sensitive screen 1004 may alsohave an area that assists a user with identifying which portion of thescreen is in focus. This could be a bar of light or in general andindicator that identifies which one or more portions of the SP touchsensitive screen 1004 are in focus. (See for example, FIG. 29)

One or more display controllers (such as display controllers 216 a, 216b and/or dedicated display controller(s) on the SP 1000) may be providedfor controlling the operation of the touch sensitive screen 1004including input (touch sensing) and output (display) functions.

In accordance with one exemplary embodiment, a separate touch screencontroller is provided for the SP 1000 in addition to each of thecontrollers for the touch screens 104 and 108. In accordance withalternate embodiments, a common or shared touch screen controller may beused to control any one or more of the touch sensitive screens 104 and108, and/or 1004. In accordance with still other embodiments, thefunctions of the touch screen controllers may be incorporated into othercomponents, such as a processor and memory or dedicated graphicschip(s).

In a similar manner, the SP 1000 may include a processor complementaryto the processor 204, either of which may comprise a general purposeprogrammable processor or controller for executing applicationprogramming or instructions. In accordance with at least someembodiments, the processors may include multiple processor cores, and/orimplement multiple virtual processors. In accordance with still otherembodiments, the processors may include multiple physical processors. Asa particular example, the processors may comprise a specially configuredapplication specific integrated circuit (ASIC) or other integratedcircuit, a digital signal processor, a controller, a hardwiredelectronic or logic circuit, a programmable logic device or gate array,a special purpose computer, or the like. The processors generallyfunction to run programming code or instructions implementing variousfunctions of the device 100 and/or SP 1000.

The SP 1000 can also optionally be equipped with an audio input/outputinterface/device(s) (not shown) to provide analog audio to aninterconnected speaker or other device, and to receive analog audioinput from a connected microphone or other device. As an example, theaudio input/output interface/device(s) 256 may comprise an associatedamplifier and analog to digital converter usable with SP 1000.Alternatively or in addition, the device 100 can include an integratedaudio input/output device 256 and/or an audio jack for interconnectingan external speaker or microphone via SP 1000. For example, anintegrated speaker and an integrated microphone can be provided, tosupport near talk or speaker phone operations.

Hardware buttons (not shown) but similar to hardware buttons 158 can beincluded for example for use in connection with certain controloperations. Examples include a master power switch, volume control,etc., as described in conjunction with FIGS. 1A through 1J. One or moreimage capture interfaces/devices 1016, such as a camera, can be includedfor capturing still and/or video images. Alternatively or in addition,an image capture interface/device 1016 can include a scanner or codereader. An image capture interface/device 1016 can include or beassociated with additional elements, such as a flash or other lightsources.

Communications between various components of the device 100 and SP 1000can be carried by one or more buses and/or communications channels. Inaddition, power can be supplied to one or more of the components of thedevice 100 and Sp 1000 from a power source and/or power control module260. The power control module 260 and/or device 100 and/or SP 1000 can,for example, include a battery, an AC to DC converter, power controllogic, and/or ports for interconnecting the device 100/1000 to anexternal source of power.

The middleware 520 may also be any software or data that allows themultiple processes running on the devices to interact. In embodiments,at least portions of the middleware 520 and the discrete componentsdescribed herein may be considered part of the OS 516 or an application564. However, these portions will be described as part of the middleware520, but those components are not so limited. The middleware 520 caninclude, but is not limited to, a Multi-Display Management (MDM) class524, a Surface Cache class 528, a Window Management class 532, anActivity Management class 536, an Application Management class 540, adisplay control block, one or more frame buffers 548, an activity stack552, and/or an event buffer 556—all of the functionality thereofextendable to the SP 1000. A class can be any group of two or moremodules that have related functionality or are associated in a softwarehierarchy.

The MDM class 524 also includes one or more modules that are operable tomanage the display of applications or other data on the screen of the SP1000. An embodiment of the MDM class 524 is described in conjunctionwith FIG. 5B. In embodiments, the MDM class 524 receives inputs from theOS 516, the drivers 512 and the applications 564. The inputs assist theMDM class 524 in determining how to display the information required bythe user. Once a determination for display configurations is determined,the MDM class 524 can bind the applications 564 to a displayconfiguration. The configuration may then be provided to one or moreother components to generate the display on the SP 1000.

FIG. 11 illustrates an exemplary embodiment showing the device 100docking with the SP 1000. More specifically, the device 100 is beinginserted into a slot (not shown) on the SP 1000. On completion of theinserting of device 100 into SP 1000 (See FIG. 12), device 100communicates with the SP 1000 via bus or other wired or wirelesselectrical means 1204. The device 100 is also connected with, forexample, the camera/video camera 1016, microphone (Mic), and power port1208.

In conjunction with the docking of device 100 with SP 1000, one or moreof the devices can begin power management. For example, one or more ofthe device 100 and SP 1000 can include power supplies, such asbatteries, solar, or in general any electrical supply, any one or moreof which being usable to supply one or more of the device 100 and SP1000. Furthermore, through the use of, for example, an AC power adaptorconnected to port 1208, the SP 1000 can supply power to device 100, suchas to charge device 100. It will be appreciated that the powermanagement functionality described herein can be distributed between oneor more of the device 100 and SP 1000, with power being sharable betweenthe two devices.

In addition to power management functions, upon the device 100 beingdocked with the SP 1000, the displays on device 100 can be turned offto, for example, save power. Furthermore, electrical connections areestablished between the device 100 and SP 1000 such that the speaker,microphone, display, input capture region(s), inputs, and the like,received by SP 1000 are transferrable to device 100. Moreover, thedisplay on device 1000 is enabled such that information that would havebeen displayed on one or more of the touch sensitive displays 110 and114 is displayed on touch sensitive display 1010. As will be discussedin greater detail herein, the SP 1000 can emulate the dual displayconfiguration of the device 100 on the single display 1010.

The SP 1000 can optionally be equipped with the headphone jack 1212 andpower button 1216. Moreover, any hardware buttons or user input buttonson the device 100 could be extended to and replicated on the SP 1000.

This dock event between the device 100 and SP 1000 can be seen as states336 or 344 in FIG. 3A. As will be appreciated, and in accordance withone of the illustrative embodiments herein, the device 100 is dockedwith SP 1000 with the device being in the open state 210. However, it isto be appreciated that the device 100 can be docked with the SP 1000 inthe closed state 304, or docked via, for example, a cable without thedevice 100 necessarily being inserted into the SP 1000.

FIGS. 13A-B illustrate application reorientation according to anexemplary embodiment of the invention. In particular, FIG. 13Aillustrates the device 100 being inserted into the SP 1000. Before beingassociated with the SP 1000, the device 100 has two applications, bothin the landscape mode, represented by application “B” in landscape on afirst screen and application “C” in landscape on a second screen(partially obscured by SP 1000).

FIG. 13B illustrates the re-orientation of the windows for the twoapplications based on the device 100 being associated with the SP 1000,the SP 1000 being in the landscape orientation. In accordance with thisexemplary embodiment, application “B” on the device 100 is re-orientedto be in the portrait orientation on the SP 1000, and in a similarmanner, application “C” on the device 100 is reoriented to the portraitorientation on the right-hand side the touch sensitive display 1010. Aswill be appreciated, the reorientation of the application(s) from thedevice 100 to the SP 1000 can occur in a similar manner for a singleapplication running on the device 100. For example, if there is only oneapplication running on device 100, and the application is running inlandscape mode, when the device 100 is docked with the SP 1000, theorientation of the application is reoriented to be appropriate for thecurrent orientation of the SP 1000. For example, if the application onthe device 100 is in portrait mode, and the SP 1000 is in landscapemode, the application is reoriented from portrait mode on the device 100to landscape mode on the SP 1000. In a similar manner, if theapplication on the device is in landscape mode, and upon being docked tothe SP 1000 in portrait mode, the application is reoriented intoportrait mode for appropriate viewing on the SP 1000.

In accordance with one exemplary embodiment, the accelerometer 176 ondevice 100 is used to determine the orientation of both the device 100and SP 1000, and consequently the orientation of the touch screendisplay 1010. Therefore, the accelerometer(s) 176 outputs a signal thatis used in connection with the display of information to control theorientation and/or format in which information is to be displayed to theuser on display 1010. As is to be appreciated, reorientation can includeone or more of a portrait to landscape conversion, a landscape toportrait conversion, a resizing, a re-proportioning and/or a redrawingof the window(s) associated with the application(s).

On reorienting of the running application(s), the application(s) isdisplayed on display 1010 on SP 1000.

In accordance with an optional exemplary embodiment, priority can begiven to the application that is in focus. For example, and using againapplications “B” and “C” as illustrated in FIG. 13B, if insteadapplication C was in focus before docking, application C could bereoriented and displayed on the left-hand portion of display 1010, andapplication B, which was not in focus before docking, displayed on theright-hand portion of display 1010 upon docking.

In accordance with another optional embodiment, the application in focuscould be displayed in full-screen mode on display 1010 with theapplication(s) not in focus placed into a window stack that is, forexample, in a carousel-type arrangement as discussed hereinafter.

FIG. 14 illustrates an exemplary embodiment of a single application modefor the SP 1000. In the single application mode, all applications arelaunched and displayed in full screen. The single application mode canbe indicated by a multi-tasking icon in the enunciator bar, or at someother location on screen 1004.

Displaying of the application(s) are managed by one or more of thedisplay controller 544, framework 520, window management module 532,display configuration module 568, as well as middleware 520 andassociated classes. In single application mode, all dual screen capableapplications can be launched in either a dual screen or max mode, wherethe application is displayed substantially filling the display 1010.This is applicable to when the SP 1000 is either in the portrait mode,as illustrated in FIG. 14, or in the landscape mode, as illustrated inFIG. 15. In these figures, the “A” represents the single applicationwith the X1, X2 being variables representing the coordinates and/orlocation of the window in which the application “A” is to be displaced.A similar notation is used hereinafter for the multi-application mode,with it being appreciated that, for example, X1 may contain thecoordinate information for the displaying of the window for a firstapplication, and X2 may contain the coordinate information for thedisplaying of a window corresponding to a second application, and so on.

Therefore, in one exemplar embodiment, when a single application isexecuted, a single application can launch in the full screen mode andcan be correlated to the max mode as discussed in relation to FIG. 6Iwhere a single application spans both screens of the device 100. Thismax mode is applicable to both the portrait and landscape orientationsas illustrated in FIG. 14 and FIG. 15 with the display configurationmodule 568 appropriately (re)sizing the window for the application tofit on substantially all or all of the display 1010.

This resizing can occur regardless of whether a native application onthe device 100 actually supports the orientation of the SP 1000.Therefore, even if the application does not support a particularorientation on device 100, the display configuration module 568 canappropriately re-render and/or re-size the window for the applicationfor appropriate display on the SP 1000.

FIG. 16 and FIG. 17 illustrate an exemplary method of rending a singleapplication, that is a dual screen application, in the portrait max modeand landscape max mode, respectively. More specifically, in FIG. 16, therendering of a dual screen application in portrait mode will display ondisplay 1010 one of the two screens substantially or completely fillingdisplay 1010. A user then, for example using a gesture, could scrollbetween the two screens of the single application. In the landscapemode, as illustrated in FIG. 17, the screen 1010 is divided into a firstportion 1704 and a second portion 1708. In this exemplary embodiment,the first screen of the dual screen application is rendered in firstportion 1704, and the second screen of the dual screen application isrendered in the second portion 1708. While a certain portion of thescreen 1010 is illustratively logically divided for the first portion1704 and the second portion 1708, it should be appreciated that thescreen real estate assigned to each portion can vary, for example, basedon one or more of optimum display for the window(s), type of informationbeing displayed in each portion, user preferences, rules associated withthe application, and/or the like.

In accordance with a first example, the first portion is allocated onethird of the screen 1010's resolution, while the second portion 1708 isallocated two thirds of the screen real estate. In accordance withanother example, the screen 1010 is split 50/50. In accordance with yetanother example, the first portion could be allocated 70% of the screen1010's real estate, while the second portion 1708 could be allocated30%. The managing and resizing of these windows can again be done incooperation with the display configuration module 568, as well as thewindows management module 532 and display controllers for successfulrendering of the location of the window(s) on the SP 1000.

As will be appreciated, and in a manner similar to the operation ofdevice 1000, should the SP 1000 change orientation (e.g., from landscapeto portrait or vice versa) the window(s) for the application(s) can beredrawn in the appropriate orientation taking into account windowprioritization based on whether a particular application and currentfocus is for a dual screen application or a single screen application.

Focus can also be taken into consideration when determining which windowof the application should be displayed when the SP 1000 is in theportrait position. For example, if the application is an e-mail client,and the application natively is displayed on dual screens on device 1000(a first screen being directed toward showing inbox content, and thesecond screen being a preview window for a specific item in the inbox)the system can evaluate which window is currently in focus, and ensurethat window is displayed in the portrait max mode when the SP 1000 is inthe portrait orientation.

In FIG. 17 the SP 1000 is configured to merge windows from the dualscreen application on to a single display 1010. In this landscapeorientation, data (e.g., a single image, application, window, icon,video, etc.) from a first window is displayed in a first portion of thedisplay 1010 while data (e.g., a single image, application, window,icon, video, etc.) is shown in a second portion of the display 1010.Similar to other output configurations, it may be possible to transitionthe SP 1000 from the shown output configuration to any other outputconfiguration described herein, depending on, for example, into whichstate the SP 1000 is moved.

Some other exemplary embodiments of windows management within the SP1000 upon the device 100 docking with the SP 1000 are as follows: Forexample, a device 100 is docked to the SP 1000, with the SP 1000 in aportrait orientation and there are two single-screen applicationsrunning on the device 1000, the application in focus is placed in alower portion of the display 1010, and the application not in focus isplaced on an upper portion of the display 1010. Another exemplaryscenario, where the device 100 is docked to a portrait-oriented SP 1000where one dual-screen application is running on the device 100 and theSP 1000 is in a dual application mode, applies gravity drop as discussedherein.

In another exemplary scenario, where the device 100 is running twosingle-screen applications, and the SP 1000 is in a landscape dualapplication mode, the first application is assigned to a first portionof the display 1010 and the second application is assigned to a secondportion of the display 1010.

In yet another exemplary scenario where the device 100 is running onedual-screen application and the SP 1000 is in dual application landscapemode, both screens of the dual screen application can be shown on the SP1000.

Stickiness can also apply to the SP 1000 such that, for example, when afirst application is in focus, upon docking to a single application modeSP 1000, the application remains visible after docking. As anotherexample of stickiness, if a second application is in focus upon dockingto a single application mode SP 1000, application two remains visibleafter docking.

In accordance with another example, the device 100 is running onedual-screen application and is docked to a landscape-oriented SP 1000 inmax mode, the windows are re-oriented to be side-by-side, opposed to oneabove the other.

FIG. 18 through FIG. 21 generally illustrate the management and displayof a virtual keyboard 1804 on display 1010. More specifically, in FIG.18, in portrait mode, the virtual keyboard 1804 is positioned belowapplication area 1808, where an application is displayed in, forexample, max mode. In general, it is preferred that the keyboard can beglued to the lower-portion of the display 1010, regardless of whetherthe SP is in the landscape or portrait mode. However, it is to beappreciated that, for example, based on user preferences, the screen canbe glued to another portion of the screen, or can be moved to anotherlocation via, for example, a gesture. In FIG. 18, the application area1808 displays, for example, a standard application with the virtualkeyboard 1804 being displayed in the lower portion of display 1010. InFIG. 19, for example, the application area 1908 is showing a dual-screenenabled application in max mode. The keyboard 1804 is again similarlydisplayed in the lower portion of the display 1010.

In FIG. 20, in SP landscape mode, the keyboard 1804 is displayed in thelower portion of display 1010 with the application area 2004substantially or completely filling the displayable area above thekeyboard 1804. In FIG. 21, the SP is again in landscape mode anddisplaying a dual-screen enabled application in max mode, theapplication area 1 2104 and application area 2 2108, the keyboard 1804is displayed below the two application areas.

In general, in the embodiments illustrated in FIG. 18 through FIG. 21, afirst determination is made as to whether a keyboard should bedisplayed. If the keyboard is to be displayed, the next determination ismade as to the orientation of the SP. If the SP is in a portrait mode,the virtual keyboard is presented also in a portrait mode, preferable onthe lower portion of the screen. If the SP is in a landscape mode, thekeyboard is optionally re-sized to be substantially displayed on a lowerportion of the display with, for example, one or more applicationwindows being located above the virtual keyboard. With the orientationof the SP change, the keyboard is also reoriented to be coincident withthe orientation of the SP. Similarly, when the keyboard is no longerrequired, the keyboard is hidden with the application area(s) beingexpanded to again substantially fill the display 1010.

FIG. 22 and FIG. 23 illustrate exemplary methods of managing windowpositions on the SP 1000. In particular, in FIG. 22, application X 2204is in view on display 1010. On receiving user input, such as the swipemotion represented by 2208 in the gesture capture region 1020,application X is “scrolled” to the left to be replaced with thedual-screen application A1|A2, as shown in FIG. 23. If the same gesture2208 were to be repeated again, application Z would come into view.Similarly, if in FIG. 22 gesture 2208 was in the opposite direction, tothe right, application Y would come into view on display 1010. Scrollingthrough available windows is of course applicable to both the landscapeand portrait mode of the SP in a similar manner. For example, inportrait mode, instead of the gesture traversing from left to right orright to left, the gesture could traverse in a downward motion, or in anupward motion, with the virtual stacks of the windows being located“above” or “below” the device, similar to a rolodex. Thus, when the userinitiates a downward type gesture, the next application “above” isdisplayed on display 1010.

FIG. 24 illustrates the multi application mode of the SP 1000, whereinin the multi application mode the SP 1000 emulates the device 100 in itsmini-tablet form—with this mode optionally being invoked by selection ofa multi application button (shown and described hereinafter). Asimplified way of understanding this mode is to appreciate that the modeemulates the device 100 being opened. In this multi application mode,the SP 1000 can inherit the rules regarding the display of informationon the device 100—For example, that all applications are launched insingle screen mode. One exception could be applications that support amax mode can be by default automatically expanded to this mode ifprovided the opportunity.

In this mode, each application has the ability to determine how theapplication appears in each orientation (e.g., portrait and landscape).

FIG. 26 illustrates an exemplary method of managing the multipleapplication mode of the SP 1000. In the multiple application mode,multiple applications can be managed and displayed within the display1010. In multi application mode, the SP1000 having the single screenemulates the dual screens of the device 100. To initiate the multipleapplication mode, a button/toggle 2618 is selected, which allows theuser to select multiple applications for display in the display 1010. Inthis exemplary embodiment, a first application 2604 C, is shown in theupper-portion of the portrait mode SP 1000 and a second application 2608D, is shown in a lower-portion of screen 1010. In conjunction with thedisplaying of multiple applications in the multiple application mode,focus indicator 2616 can be provided to assist the user with identifyingwhich application is in focus. As discussed, this focus indicator can bea light bar, or other indicator (such as an indicator in the screen 1010or beside 2608) drawing the user's attention to which application is infocus. In the exemplary embodiment in FIG. 26, application D 2608 is infocus as represented by the focus bar 2616. In accordance with thisexemplary embodiment, and while the focus bar 2616 is shown in thegesture capture region 1020, it should be appreciated that the focusindicator could be located in some other portion of the SP 1000. Forexample, the window for the application in focus could be slightlyre-sized to allow for the display of a bar of pixels adjacent to thewindow, which would similarly alert the user to the fact that thatapplication is in focus. Similarly, the application in focus couldappear at normal brightness while the application not in focus could beslightly dimmed. In general, any technique could be used to assist theuser in readily determining which application is in focus.

To change focus, a user could use any of the gestures discussed hereinor could, for example, simply touch the area where application C isdisplayed, thereby changing focus to application C, at which point acorresponding relocation of the focus indicator 2616 to adjacent toapplication C would occur.

FIG. 27 illustrates a similar scenario for a landscape mode SP 1000. Inparticular, and upon selection of the multi application mode, thedisplay 1010 is divided between, in this example, a first application D2712, and a second application F 2708. Here, application D is displayedon the right-hand portion of display 1010 and application F displayed onthe left-hand portion of display 1010. While in this exemplaryembodiment, the display real estate is split 50/50 between the twoapplications, it should be appreciated that one application could bedisplayed on a larger portion of the display 1010 than the other. Inthis particular exemplary embodiment, application D is in focus, asrepresented by focus indicator 2416.

In the multiple application mode, in both portrait and landscapeorientations, each application could have its own associated windowstack as show in FIG. 22 and FIG. 23, or there could be one stack sharedbetween all of the displayed applications. More specifically, if eachapplication has its own stack, with a stack structure similar to thatillustrated in FIG. 22, a stack would be available for the firstapplication, such as application C, and a similar stack would beavailable for application D. Each of these stacks could be independentlyscrolled through using, for example, a gesture as discussed above.

FIG. 28 illustrates an exemplary method for managing screen displaycharacteristics according to another embodiment of this invention. Inaccordance with this embodiment, a determination is made whether anapplication can be maximized, and if it can be maximized, it is expandedto the dual screen mode or max mode, as appropriate, to substantiallyfill the display 1010 as illustrated in the figure. Here, applicationE1, which is an application that can be maximized, has been expandedusing the max mode to substantially or completely fill display 1010.

In FIG. 28, button 2618 allows a user to toggle between a single screenmode (as illustrated in FIG. 28) and an emulated dual screen mode, forexample, as illustrated in FIG. 26 and FIG. 27. Here, button 2618 doesnot include the “|” therefore indicating to the user the SP 1000 is insingle screen mode.

FIG. 29 illustrates an exemplary method of managing windows. In thisexemplary embodiment, and similar to the operation of the device 100,when the last application in the stack is moved to the side, the desktopis displayed. Even more specifically, as shown in FIG. 29, application F2908 is displayed in an upper portion of display 1010 and the desktop2912 is displayed in the lower portion of display 1010. Here the desktopis in focus, as illustrated by the focus indicator 2916. Thisconfiguration is available since the user has selected the dual-screenemulation mode button 2618.

FIG. 30 illustrates an exemplary method of displaying a keyboardaccording to one embodiment. In particular, when the SP is in portraitmode, the SP will have a keyboard area 3004 and an application area3008. Upon display of the keyboard 3004, the application in applicationarea 3008 is resized to substantially or completely fill the area of thescreen not occupied by the keyboard 3004.

FIG. 31A and FIG. 31B illustrate desktop availability in both the singleapplication mode and dual application mode in both the SP landscape modeand SP portrait mode. In particular, and in accordance with an exemplaryembodiment, the desktop 3104 will occupy the entirety of the screen1010. Additionally, and in accordance with this exemplary embodimentwhere the desktop is shown in a full-screen mode, the enunciator bar1312 can be expanded across the entirety of the screen 1010. This canoccur in both the portrait mode as shown in FIG. 31A as well as thelandscape mode as illustrated in FIG. 31B. From here, upon selection ofthe application launcher 3116, the application launcher can optionallyexpand across the entirety of the screen 1010 in either the portrait orlandscape mode. Similarly, the file explorer, which is launched bypressing the file explorer button 3120, can be similarly expanded intosubstantially all or all of the screen 1010 space.

FIG. 32A and FIG. 32B illustrate screen redrawing that may required totransition the desktop from the device 100 to the SP 1000. Inparticular, in FIG. 32A, six exemplary desktop panels are shown3204-3224. These desktop panels are moveable in a carousel-like fashionbased on gesture input from a user. However, it may not be possible todirectly translate these panels to display correctly on the SP 1000without the panels being distorted or not occupying the entirety of thescreen 1010. Accordingly, in accordance with one exemplary embodiment,one or more of the panels 3204-3224 can be resized when displayed on theSP 1000 to accommodate all or substantially all of the screen 1010. Inaccordance with another exemplary embodiment, more than two of thepanels can be shown on the screen 1010, such as a portion of panel D23208, a portion of panel D3 3212 and a portion of panel D4 3216. In thismanner, the desktop illustrated on the SP 1000 will have a similarlook-and-feel to the desktop panels shown on device 100. The samecarousel-like motion is available via a gesture input to the SP 1000such that a user can scroll to the one or more panels of the desktop.

FIG. 33 illustrates an exemplary notifications display that behaves onthe SP 1000 in a very similar manner to that of the device 100. Inparticular, and whether in the portrait or landscape mode, notificationsand status/toggle buttons are provided that allow the user to, forexample, toggle on or off Bluetooth®, WiFi, screen lock, dual or singlescreen mode, power options, and the like. These, as well as otheroptions, are generally shown in area 3304. Additional notifications canalso be shown in area 3308 including one or more of carrier information,notification information, communication information, and the like asdiscussed above.

In more detail, area 3304 provides some buttons for standard widgetssuch as WiFi toggle on and off, Bluetooth® toggle on and off, and thelike. The screen lock toggle can allow, for example, user to lock thescreen thereby prohibiting it from rotating despite the orientation ofthe SP 1000. The toggle can change color or display characteristics toindicate whether screen lock has been enabled. The single/dualapplication mode button toggles, for example, three different statesincluding a dual application mode state, a single application modestate, and a single application lock state. The power mode toggletoggles between a handset optimized, SP optimized, hybrid powerconsumption, or of the like. These power modes can be associated withpower levels, as indicated by the two battery status indicators 3312 and3316 which correspond to the power levels in the device 100 and SP 1000,respectively.

FIG. 34A and FIG. 34B show exemplary methods of launching and displayingthe application launcher upon selection of the application launcherbutton 3116. In both the portrait mode illustrated in FIG. 34A andlandscape mode illustrated in 34B, and when the SP is in singleapplication mode, the application launcher can appear in a bubble so asto not necessarily take up the entirety of the screen 1010. However, forexample, upon receiving an appropriate gesture or input by the user, theapplication launcher can be expanded to take up the entirety of thescreen 1010. This could further be classified in a preference such thatthe default is to always open the application launcher in a bubble so asto not take up the entirety of the screen 1010, or to always open infull screen mode, taking up substantially all or all of the screen 1010.

FIG. 35A and FIG. 35B illustrate an optional embodiment whereby thesystem could provide “hints” as to the content of desktop panels thatare not fully in view. More specifically, FIG. 35A shows the firstembodiment of the desktop panels D1-D6, 3504-3524 respectively. Asdiscussed, a user is able to scroll through these panels in acarousel-type fashion, revealing any of the content in D1-D6. Inaccordance with the optional embodiment illustrated in FIG. 35B, wherethe same panels D1-D6 are available for viewing by user, the user isgiven a preview of one or more adjacent panels, here D2 3508 and D53520. In this configuration, this user is able to “peek” at the contentof the adjacent panel(s) without necessarily scrolling in a carousellike fashion to view the entirety of the panel. More specifically, theentirety of panel D3 3512 and D4 3516 is shown on the display 1010. Inaddition, approximately one third of panel D2 3508 and one third ofpanel D5 3520 are also shown on the display 1010. As will beappreciated, more or less of panels D2 and D5 could be shown, with thegreater of the panel being shown, the more visibility into that portionof the desktop the user would have.

FIG. 36 illustrates an optional embodiment for managing in a multipleapplication mode the stack of windows. This elegant method reinforcesthe conceptual model and assists the user with visualizing spatially the“carousel” type arrangement of the stack in the multi application mode.As is to be appreciated, while the exemplary embodiment shown in FIG. 36is directed toward portrait mode of SP1000, it can work equally well inthe landscape mode with the difference being instead of the carouselrotating from a top to bottom or bottom to top type arrangement, the“carousel” could be manipulated in a left to right or right to left typeoperation. However, the carousel could also work in a top to bottom orbottom to top mode in landscape mode as well.

In this exemplary embodiment, when multi-application mode is enabled viabutton 2618, application C 3604 and application D 3608 can be displayed,separated by separator 3612. In accordance with this optional exemplaryembodiment, there are also one or more overflow applications behindapplication C 3604, here the overflow applications being 3424 and 3428.In a similar manner, there can be one or more overflow applicationsbehind application D 3608, here application 3416 and application 3420.In this particular exemplary embodiment, the back and menu buttons 3432can be enabled with a portion of the desktop 3436 being viewable behindthe application stack. Upon receipt of one or more input gestures, suchas gesture 3440, a user can scroll through the “carousel” ofapplications, in this instance, relocating application D 3608 toapplication C 3604's position, and thereby revealing application 3416.In addition, the focus indicator can be displayed near the applicationthat is in focus. In this particular example, focus indicator 3444 isdisplayed beside application D. In accordance with an optional exemplaryembodiment, instead of the stack “stopping” when the user reaches thelast application, such as application 3420 or application 3428, theapplications can be stacked in a circular manner, and continuouslyrotate in response to one or more input gestures by a user.

These concepts can be extended to the situation where the keyboard isalso displayed in the multiple application mode. For example, and asillustrated in FIG. 37, the keyboard 3704 is displayed below theapplication stack 3708. “Behind” the application stack 3708, areadditional applications 3712 and 3716 that the user can access via, forexample, initiation of gesture 3720. This exemplary embodiment has theapplications scroll in a carousel-like fashion into and out of view,with the keyboard 3704 remaining visible, for example, at the bottom ofdisplay 1010. As with the embodiment in FIG. 35, the back and menubuttons can be enabled and, for example, virtually displayed on thedisplay 1010 as illustrated by graphical button 3724.

FIG. 38 outlines an exemplary method for docking the device 100 with thesmartpad 1000. In particular, control begins in step S3802 and continuesto step S3804. In step S3804 the insertion of the device into the SP isdetected. Next, in step S3806, power management can optionally begin.For example, and as discussed, the SP can be used as a power source forthe device, the device can be used as a power source for the SP, powercan be shared between the two devices and/or the SP can be plugged in,via for example, an AC adaptor, which is capable of charging one or moreof the SP and the device 100. Then, in step S3808, the display of thedevice 100 is optionally turned off to, for example, conserve power.Control then continues to step S3810. In step S3810, communicationand/or connectivity are established between the device 100 and the SP.Next, in step S3812, display and other input/output functions on the SPare enabled. Then, in step S3814, the device software settings aremapped to the smartpad hardware settings. Control then continues to stepS3816.

In step S3816, the screen orientation of the device is automaticallyaligned to the orientation of the SP. Next, in step S3818, the lastapplication in focus on the device remains in focus and is displayed onthe SP. Normal operation and interaction with the SP then continuesutilizing, for example, the same gestures as are usable with the device100. Control then continues to step S3820 where the control sequenceends.

FIG. 39 illustrates an exemplary method of application/displayorientation/reorientation. In particular, control begins in step S3900and continues to step S3902. In step S3902, the orientation of the SP isdetected. Next, in step S3904, the application orientation on the deviceis detected. Then, in step S3906, one or more displayed applications arereoriented to be in the same orientation as the SP. In addition, andbased on the need for reorientation, a re-drawing or re-sizing of theapplication can also occur with the application(s) being displayed onthe SP. Control then continues to step S3908 where the control sequenceends.

FIG. 40 outlines an exemplary method for managing the keyboard. Inparticular, control begins in step S4000 and continues to step S4002. Instep S4002, determination is made as to whether a keyboard request hasbeen detected. If a keyboard request has not been detected, controljumps back to step S4000 with control otherwise continuing to stepS4004. In step S4004, a determination is made as to the orientation ofthe SP. If the SP is in the landscape orientation, control jumps to stepS4010 with control otherwise continuing to step S4006 with the SP beingin the portrait orientation. In step S4006, the keyboard is displayed inthe portrait mode.

Next, in step S4008, a determination is made as to whether there hasbeen an orientation change. If there has been an orientation change,control jumps to step S4010 with control otherwise continuing to stepS4014.

In step S4010, the keyboard is displayed in the landscape mode. Next, instep S4012, a determination is made as to whether there has been achange in orientation of the SP. If there has been a change in theorientation, control jumps to step S4006 with control otherwisecontinuing to S4014.

In step S4014, a determination is made as to whether the keyboard shouldbe hidden. If the keyboard should be hidden, control continues to stepS4016 with control otherwise continuing back to step S4004.

In step S4016, the keyboard is hidden with control continuing to stepS4018 where the control sequence ends.

FIG. 41 illustrates an exemplary method for window management. Inparticular, control begins in step S4100 and continues to step S4102. Instep S4102 a gesture is detected. As will be appreciated, and similar tothe device 100, this gesture can be on the touch-sensitive display, in aconfigurable area, and/or in the gesture capture region(s). In stepS4104, gesture direction can also optionally be detected. Then, in stepS4106, the next application window can be brought into view, enabling,for example, a user to scroll through application window stack. Adetermination is then made as to whether another gesture has beendetected. If another gesture has been detected, control jumps back tostep S4104 with control otherwise continuing to step S4110.

FIG. 42 outlines an exemplary method for screen management. Inparticular, control begins in step S4200 and continues to step S4202. Instep S4202, multiple application mode is enabled via, for example,selection of a button or toggle. Next, in step S4204, a user isoptionally prompted to select which applications will be displayed. Inan alternative embodiment, two adjacent applications in the stack aredisplayed, with one of the applications being the application that iscurrently in focus. Then, in step S4206, the screen is split with thefirst portion of the screen displaying a first application and a secondportion of the screen displaying a second application. Next, in S4208,the application that was detected to be in focus is then highlighted onthe SP in step S4210. Control then continues to step S4212.

In step S4212, a determination is made as to whether a new applicationhas been brought into focus. If a new application has been brought intofocus, control jumps back to step S4210 where that application ishighlighted with an “in-focus” indicator. Otherwise, control continuesto step S4214 where the control sequence ends.

FIG. 43 outlines an exemplary method for windows management. Inparticular, control begins in step S4300 and continues to step S4302. Instep S4302, a determination is made as to whether the application can bemaximized. Next, in step S4304, if the application is maximizable,control jumps to step S4306 where the application is expanded to eitherthe dual screen mode or the max mode. Control then continues to stepS4308 where the control sequence ends.

FIG. 44 outlines an exemplary method for transitioning from anapplication window to the desktop. In particular, control begins in stepS4400 and continues to step S4402. In step S4402, the last applicationin the application window stack is detected. Next, in step S4404, agesture is detected, the gesture requesting a “next” window, however thecurrent window is the last application in the window stack. In thisscenario, in step S4406, the desktop is displayed in that there are nofurther windows to display in the application window stack. Control thencontinues to step S4408 where the control sequence ends.

FIG. 45 illustrates an exemplary method of emulating the multi-screendisplay of the device 100 on the SP1000. In particular, control beingsin step S4500 and continues to step S4502. In step S4502, the desktop isdisplayed on the SP. Next, in step S4504, the desktop is logicallydivided on the SP into, for example, two sections. Then in step S4506, afirst screen of the desktop is displayed in a first logical portion ofthe SP display. Then, in step S4508, a second screen of the desktop isdisplayed in a second logical portion of the SP display. Control thencontinues to step S4510.

In step S4510, carousel movement of the “panels” shown in the displaycan be initiated through user input, such as a gesture. Control thencontinues to step S4512 where the control sequence ends.

FIG. 46 outlines an exemplary method of displaying multiple “panels” ofthe desktop on the SP. In particular, control begins in step S4600 andcontinues to step S4602. In step S4602, a portion of the desktop isdisplayed on the SP. Next, in step S4604, the desktop is logicallydivided on the smartpad to accommodate multiple desktop “panels.” Then,in step S4608, the first screen or panel of the desktop is displayed inone logical portion of the SP display. Then, in step S4610, a secondscreen or panel of the desktop is displayed bridging a first and asecond logical portion of the SP display. Then, a third screen or panelof the desktop is displayed in the second logical portion of the SPdisplay. Control then continues to step S4614.

In step S4614 carousel movement of the panels can be affected by, forexample, an input of a gesture by the user. Control then continues tostep S4616 where the control sequence ends.

FIG. 47 outlines an exemplary method of displaying one or more portionsof the desktop. In particular, control begins in step S4700 andcontinues to step S4702. In step S4702, an access request to the desktopis detected. Next, in step S4704, at least one desktop panel isdisplayed. Then, in step S4706, at least one additional desktop panel ispartially displayed on the desktop. Control then continues to stepS4708.

In step S4708, and upon detection of a gesture, the partially displayedpanel can be completely displayed on the display of the SP. Control thencontinues to step S4710 where the control sequence ends.

FIG. 48 outlines an exemplary method of windows management in multipleapplication mode. In particular, control begins in step S4800 andcontinues to step S4802. In step S4802, multiple application mode isentered. Next, in step S4804, the windows stack is arranged with one ormore applications being partially visible behind a first application.Next, in step S4806, the stack can be arranged with one or moreapplications also partially being visible behind a second application.Then, in step S4808, and upon receiving an input gesture from a user,carousel-like scrolling can be enabled through the stack until the endof the stack is reached, or in a second embodiment, the stack can have a“circular” arrangement where continuous scrolling through the stack ispossible. Control then continues to step S4810 where the controlsequence ends.

FIG. 49 illustrates another exemplary embodiment of the device 100 andSP 1000 in greater detail. As illustrated, the device 100 is beinginserted into a slot (not shown) on the SP 1000. As discussed, and uponcompletion of the inserting of the device 100 into the SP 1000, thedevice 100 communicates with the SP 1000 via one or more wired orwireless electrical means, such as communication link as illustrated inthe figures. As will be appreciated however, communication can beginbefore or during insertion of the device 100 into the SP 1000.

In accordance with one exemplary embodiment, the SP 1000 includes acamera 1016, headphone jack 1212, microphone jack 4914, power port 1208,line-in jack 4018, and power button 1216. In this exemplary embodiment,a button, 4910, such as a capacitive button, allows switching betweenapplication modes. For example, activation of this button can cause theSP 1000 to switch to a single application mode, multi-application mode,or toggle between modes. For example, with a single touch, the SP 1000device automatically switch to single application mode. With two quicktouches, the SP 1000 could switch to multi-application mode. In analternative exemplary embodiment, button 4910 can be programmed to alterany function(s) of the SP 1000 and can optionally, for example, beprogrammed by a user.

The headphone jack 1212 can be any headphone jack including standard 3.5mm jacks, 2.5 mm jacks, and quarter-inch jacks. In addition, the SP 1000can be equipped such that audio information can be communicatedwirelessly to a user's headphones, with the wireless capabilityoptionally be provided in addition to the headphone jack 1212.

The power button 1216 can be a mechanical, semi-mechanical, touchsensitive, or other style button that allows a user to either turn poweron or power off to the SP 1000. In addition, the power button 1216 canbe used to place the SP 1000 in a sleep or hibernate mode.

The image capture interfaces/devices 1016, as discussed, can capture oneor more of still image information, video information, as well as otherinformation such as information associated with a code, such as abarcode, QR code, or the like in conjunction with a code readerapplication (not shown).

In addition, the SP 1000 can be equipped with near field communicationcapabilities that allow, for example, the SP 1000 to communicate withone or more other devices. In accordance with one exemplary embodiment,the SP 1000 and the device 100 both include near field communicationcapabilities such as they are able of communication with one another,and/or one or more other devices either individually, or on their own.As discussed, this capability can be used optionally in conjunction withone or more other communication protocols such as Bluetooth®, Wi-Fi and,for example, 4G LTE.

FIGS. 50A-50B illustrates exemplary operations that can occur when adevice 100 is docked into the SP 1000. As one examples of dockingactivity, automatic screen orientation event(s) can occur to align thedevice 100 displays to that of the SP 1000 orientation. This activitywould be initiated upon the detection of a docking event. As anotherexample, the last application in focus on the device 100 can continue tobe in focus on the SP 1000. As yet another example, applications on thedevice 100 that need to degrade in experience can do so elegantly,taking into account new or different hardware, such as a video camera,and the SP 1000 hardware capabilities.

As an even further example, one or more software settings on the device100 can be mapped to the new hardwarecapabilities/requirements/limitations on the SP 1000, and can optionallyautomatically be adjusted to ensure compatibility (to the extentpossible) with the hardware on the SP 1000. Moreover, and as previouslydiscussed, one or more of wired and/or wireless communications can beestablished as the docking event between the device 100 and the SP 1000occurs.

As illustrated in FIG. 50B, and upon docking of the device 100 into theSP 1000, one or more applications can also automatically re-orient tothe appropriate orientation based on the current status of the SP 1000.As illustrated in FIG. 50 b, there are two applications running on thedevice 100, “A Landscape” and “B Landscape.” The “A Landscape”application is re-oriented for display on the SP 1000 as a portraitapplication, here, “A Portrait.” In a similar manner, the “B Landscape”application is re-oriented into a right-hand portion of the SP 1000display in the portrait mode, here “B Portrait.”

In accordance with an optional exemplary embodiment, the SP 1000behavior changes in relation to how the power button 1216 behavesrelative to state of the SP 1000, the state of the device 100, and/orone or more docking events. More specifically, when the SP 1000 does notcontain a docked handset, the power button behaves as follows (the timesindicated below being arbitrary and capable of being any length oftime):

For a short press or tap, the onscreen display of the SP 1000 can beshown provided there is sufficient charge.

For a medium press, such as a one second hold of the power button, SP1000 can show the onscreen display. Again, if there is sufficientcharge.

For a long press, such as a 12 second hold, again the onscreen displaycan be shown if there is sufficient charge.

Alternatively, if the SP 1000 is already on, pressing of the powerbutton can transition the SP 1000 to either a stand-by, hibernate, oroff state.

In accordance with another exemplary embodiment, where the SP 1000contains an active device 100 that has been docked with the SP 1000, thepower button can behave in exactly the same manner as the power buttonon the device 100. For example, a short tap or press can toggle thestand-by mode. A medium press, if in stand-by mode, then awakes thedevice. If active, a medium press can display device power menu. In thisstate, a long press could, for example, trigger a hard reset.

When a powered-off device 100 is docked with the SP 1000, in accordancewith one exemplary embodiment, engaging of the power button will alwaysactivate the device regardless of press length. For example, a shortpress or tap will power on the device 100. Similarly, a medium press orlong press will also power on the device 100.

When docked, typically only the settings that are available on the SP1000 will be available to be viewed or changed. In the case of uniquesettings, the SP 1000 settings can be shown. Furthermore, when there isa competing, conflicting, or non-equivalent feature in the device 100,the SP settings can govern. Similarly, when undocked, only the settingsthat are available on the device 100 will be available to view orchange, and in the case of unique settings, the settings on the device100 will be shown.

FIG. 51 illustrates an exemplary state of the SP 1000 during a chargingevent. Here, the battery on the SP 1000 has been depleted, and it is ina charging state as indicated by the lightning bolt icon as shown in thedisplay 1010. In conjunction with the lightning bolt icon, it should beappreciated that a battery icon 5104 can also be displayed, here shownwith two bars indicating the battery is approximately 30% charged and ina charging state. In conjunction with a optional embodiment a batteryicon 5108 can also be displayed, here shown with three bars indicatingthe battery is approximately 60% charged and in a charging state for thedocked device 100.

The SP 1000 can also be docked to a dock 5112 that allows one or more ofcharging of the SP 1000 and device 100, as well as connectivity via oneor more of a USB port, charger port, video connector and audio ports.

FIG. 52 illustrates another exemplary embodiment, where the SP 1000 isnot docked with the device 100, and here the battery status indicator isshown illustrating that the SP 1000 contains approximately a 30% charge,and that it is not charging, by lack of the lightning bolt icon beingdisplayed.

In FIG. 53, an optional indicator 5304 can be provided on display 1010indicating whether the SP 1000 is in a docked or undocked state. Asdiscussed above, this can have an effect on how charging occurs as wellas if and when power should be shared between the SP 1000 and the device100, or vice versa. In FIG. 53, the SP 1000 is shown in a chargingstate, with the battery being approximately 60% charged.

In accordance with one optional embodiment, the display 1010 can includemultiple graphical representations of charged state of one or more ofthe device 100 and SP 1000 when the device 100 is docked in the SP 1000.For example, the charge state of the device 100 can be illustrated onthe display 1010, optionally in conjunction with the charge state of theSP 1000, as discussed above.

In the situation where the power supply may not have enough power tocharge both the SP 1000 and device 100 simultaneously, one or more ofthe devices can regulate a priority charging protocol, where, forexample, either based on user or device preferences, either the SP 1000or device 100 is charged first, and the other device is charged, asneeded. This can similarly be indicated by a graphical representation inthe display 1010, showing, for example, which device is currently beingcharged, the amount of time left to charge, and a total amount of timeleft before both devices are charged.

FIG. 54 illustrates exemplary icons that can be associated with theabove-described operations. For example, where a handset such as device100 is being charged by the SP 1000, the first icon associated with thephone or device 100 is shown with the charging “lightning bolt” and thecharged status of the SP 1000 is shown in a charged, but depletingstate. In a second scenario, both the device 100 and SP 1000 are shownin a charging state. In a third scenario, where both the device 100 andSP 1000 are depleting, icons illustrating a charged, but depleting statecan be shown, for example, on the display 1010.

In a first battery charging mode, where the mode is set for deviceoptimized, priority is given to the device 100 so as to charge it beforecharging the SP 1000. Icons illustrating this priority can be shown asdisplay 1010 as discussed. Similarly, if running in an SP optimizedmode, an icon highlighting the fact that the SP 1000 will charge beforethe device 100 can be used to illustrate the charging protocol.

Battery level status indicators can also be shown for both devices, forexample in a status tray. For example, one or more levels, with afurther indicator when a warning threshold has been reached, can beshown for one or more of the devices. Similarly, low, medium, and fullbattery charge states can also be indicated for one or more of thedevices on the display 1010 and/or in a status tray.

FIGS. 55-67 illustrate exemplary keyboard placements and orientations.In FIG. 55, in portrait mode, the virtual keyboard 5504 is positionedbelow the application area 1808. In general, it is preferred that thekeyboard 5504 be glued to the lower-portion of the display 1010,regardless of whether the SP 1000 is in the landscape or portrait mode.However, it is to be appreciated that, for example, based on userpreferences, application preferences, or a combination thereof, thekeyboard can be glued to any other portion of the display 1010 or can becustomized and relocated to another portion of the display based on, forexample, a gesture.

In FIG. 55, the application area 1808 displays, for example, a standardapplication with the virtual keyboard 5504 being displayed in the lowerportion of the display 1010. This virtual keyboard, as discussedhereinafter, can take on a number of different configurations and iscapable of being dynamic based on one or more of the state of the SP1000, the state of the device 100 and/or one or more applications thatare currently active.

In this exemplary embodiment, the virtual keyboard 5504 takes upapproximately 30% of the display area 1010 with the application area1808 consuming the remaining approximately 60%. Here, the SP 1000 isrunning in a single application mode, with the single, activeapplication being resized and displayed in the application area 1808.This insures the entirety of the application is still visible, while theSP 1000 also displays the virtual keyboard 1804. In accordance with anoptional embodiment, the keyboard is overlayed, with a percentage oftransparency, over the application area 1808 such that the underlyingapplication can still be seen.

FIG. 56 illustrates another exemplary embodiment where the SP 1000 is ina portrait orientation, and in a dual- or multi-application mode. Inthis exemplary embodiment, application area 1 is resized and preservedfor viewing, while application areas 2-N become partially obscured bythe virtual keyboard 5604. In accordance with an optional embodiment,the application(s) at the bottom of the display 1010 can be dimmed outand remain inactive until the virtual keyboard 5604 is dismissed.

FIG. 57 illustrates an exemplary embodiment where the SP 1000 is intablet-landscape mode, with a single-application running in applicationarea 2004. In this mode, the virtual keyboard 1804 can consume, forexample, anywhere from approximately 40 to approximately 80% of thedisplay 1010. In accordance with one exemplary embodiment, the virtualkeyboard 1804, via a gesture, can be one or more of moved and zoomed todifferent locations within the display 1010, to, for example, show moreof the applications in area 2004.

In FIG. 58, when the SP 1000 is in a landscape orientation, in adual-application mode, the keyboard 1804 can be identical to thekeyboard discussed above, with either one of the applications in viewhaving keyboard focus. In this exemplary embodiment, application area1204 is in focus, and is therefore associated with input from thekeyboard. Here, application area 2208 through application area N are notin focus, and can optionally be dimmed to assist the user withunderstanding which application is associated with receiving input fromthe keyboard 1804. As with the above embodiment and via, for example, agesture, the keyboard 1804 can be manipulated, such as zoomed orrepositioned with the corresponding application area(s) and/or resizedto consume more or less of the display 1010.

FIGS. 59-67 illustrate exemplary keyboard layouts, some of the keyboardlayouts being dynamically chosen based on, for example, an activeapplication. In accordance with one exemplary embodiment, the defaultkeyboard layout can contain the following keys. Character keys: Theseare regular character keys such as those found in the QWERTY standardkeyboard with input from them being input into, for example, an in focusinput field. These character keys can be, for example, colored lightgrey and are also capable of being dynamic, as discussed hereinafter,and can be replaced by other keys when a keyboard layout changes. Theshift key modifies the character keys to allow for upper-case letters.Double-tapping on the shift key can lock the device into a CAPS-lockstate. A number-punctuation key (?123) can change the character keysinto a set of numbered and punctuation keys. Other common keys are acomma key, a space-bar key, a period-key, an enter-key, where the labelon the enter-key can be dependent on the input field's properties.Additional common keys are a delete key, a back arrow key, a slider bar,and a tab-key that allows the input focus to step to the next field in amulti-field form.

As illustrated in FIG. 59 a slider bar 5902 is shown that allows forselection of the various slider bar keys 5908. As shown in FIG. 59,slider 5902 is in the default (center) location and the keyboard 5904 isa standard QWERTY keyboard. As discussed hereinafter, the slider-bar5902 can be manipulated by, for example, a gesture or selection by theuser on the touch-sensitive display 1010. While three selectable regionsare shown on the slider bar 5902, (corresponding to 3 separate sets ofslider bar keys 5908) it should be appreciated that any number ofselectable combinations of slider bars and keys can be shown. Similarly,for each of the different types of keyboards described, there could bean associated set of slider bar keys. Optionally, the set of slider barkeys can be keyboard agnostic.

FIG. 60 illustrates an exemplary uppercase layout of a keyboard. Here,the keys 6004 are in capitals and again, in accordance with thisexemplary embodiment, the slider-bar 5902 is highlighted and in thecenter position. In this exemplary embodiment, the “shift” key ishighlighted indicating the keyboard is in a caps-lock mode withselecting of the shift key toggling the keyboard back to normal,lower-case format.

FIG. 61 illustrates an exemplary keyboard in a punctuation/numberlayout. Here, the punctuation/number keyboard layout contains an ALT keythat modifies the character keys to an alternative set of punctuationkeys, and an ABC key that modifies the character keys back to thestandard keyboard layout. As illustrated in this exemplary embodiment,the slider-bar 5902 defaults to another location within the slider barhighlighting the fact that another set of slider keys is shown.

In conjunction with this punctuation/number layout, alternative keyssuch as .com, .net, direction arrows, slash signs, and the like, thatare commonly used with internet navigation, are also provided.

In accordance with an optional embodiment, blank keys can be provided inone or more of the slider and keyboard area than can be customized by auser.

FIG. 62 illustrates a secondary or alternative punctuation layout. Here,the secondary/alternative punctuation layout contains secondarypunctuation keys, which can also include optional currency symbols, andan ALT key which modifies the character keys into the primary set ofpunctuation keys. Note that the ALT key can optionally be highlightedwhen this particular layout is shown on the display 1010. The ABC keymodifies the character keys back to the standard keyboard layout andadditional punctuation keys are provided where tapping of the “ . . . ”key 6202 can bring up even further punctuation keys.

FIG. 63 illustrates a first exemplary contextual layout keyboard. Inthis particular exemplary embodiment, the keyboard is the messaginglayout that is used for, for example, composing SMS and instantmessages. This layout can include optional keys, such as the smiley key6302, with the slider bar illustrated in another position indicatingthat another set of slider keys are shown.

FIG. 64 illustrates an exemplary URL keyboard layout. This exemplarykeyboard can be used, for example, whenever URL's are entered. Thislayout contains a slash key 6402 and a go key 6404 which replaces thestandard enter key.

FIG. 65 illustrates an exemplary e-mail keyboard layout that is usedfor, for example, entering e-mail addresses. This layout contains thefollowing special key, 6502, where the comma key is replaced with an “@”symbol 6502.

FIG. 66 illustrates an exemplary web form layout, with this layout beingdisplayed when a multi-field web form is displayed in a web browser andone of the input fields is selected. The web form layout shown here isidentical to the default layout with the slider bar 5902 having selectedthe number bar 6604 as the slider bar keys.

As is to be appreciated, this slider may not be limited to anyparticular number of corresponding keys as shown in, for example, thenumber bar position 6604, rather any number of slider bars withcorresponding key sets can be created that have any number of keys. Asyet another option, there can be 2 or more rows of keys in the sliderbay 6604.

Utilizing gesture or other selection means, the selection of any one ofthe representative block 6604 brings up a corresponding set of keys. Inthis manner, the keys associated with the selected slider bar can beindependent of the keys shown in the various keyboard configurationsdiscussed above. Moreover, the selection of the slider can be dynamicbased, for example, on the application in focus.

FIG. 67 illustrates an exemplary numerical layout for a keyboard. Here,and in addition to the number key 6702, a space bar 6704 is provided aswell as pause, wait, and next keys. As with the other embodiments, thisnumber layout can be associated with any of the keys corresponding to aselected slider bar.

FIGS. 68 and 69 illustrate exemplary methods of managing windowpositions on the SP 1000. In particular, in FIG. 68, application “X”2204 is in view on display 1010. On receiving user input, such as agesture or swipe motion represented by 2208 in the gesture captureregion 1020, application X is “scrolled” or moved to the left to bereplaced with the dual-screen application A1|A2, as shown in FIG. 69. Ifthe same gesture 2208 were to be repeated again, application Z wouldcome into view. This type of action allows “scrolling” through one ormore of the applications in the application stack. As previouslydiscussed, the applications can be stored or represented linearly innature, where in accordance with this exemplary embodiment application Yis on one end of the stack, and application Z on the other end of thestack. Upon reaching the end of the stack, one or more of audio orvisual feedback could be presented to the user indicating that they havereached the end of the stack.

In accordance with an optional embodiment, the applications revolve in a“Rolodex” type fashion such that after application Z is reached, and theuser “scrolls” to the left again, application Y would be presented. Asillustrated in FIGS. 68-69, the stepwise process to initiate movementand display to another application in the stack commences with a gesturein one or more of the gesture capture region 1020 and touch sensitivedisplay 1010 as represented by item 2. Here, the active application X,represented by item 1, can gradually transition off the display 1010, ordisappear in favor of the dual-screen application which is illustratedin max mode, as illustrated by item 3 in FIG. 69. Repeating of thissequence of steps 1, 2, 3, would bring application Z into view on thedisplay 1010 in max mode, since it is a single screen application.

FIGS. 70 and 71 illustrate docking to a portrait tablet in dualapplication mode. Here, when the device 100 is docked to a portrait SP1000, the device is always in a portrait dual orientation. Upon docking,the applications need to be re-oriented on the SP accordingly, this isconsidered a counter-clockwise rotation of the displayed information ondevice 100. If the SP was last used in single application mode, the modewould be remembered upon a re-docking event occurring with the device100.

As shown in FIG. 70, the device 100 with two single-screen applicationsis docked to a portrait as SP 1000 in dual-application mode. Here, focusremains on the application that was in focus on the device 100. Here,active application 1 on device 100 remains as active application 1 on SP1000. In FIG. F1, device 100 with one dual-screen application is dockedto a portrait SP in dual-application mode. Here, gravity drop is appliedso that application 1.2 fills the display on SP 1000.

FIG. 72 illustrates docking to a landscape SP running in dualapplication mode. Here, when the device 100 is docked to a landscape SP,the device is always in landscape dual orientation. Upon docking, theapplications on the device need to be re-oriented on the SP accordingly(this is considered a counter-clockwise rotation of the device). If theSP was last used in a single application mode, the mode could beremembered upon a re-docking of the handset. As more particularlyillustrate in FIG. 72, the device 100 with two single-screenapplications is docked to a landscape SP in dual-application mode. Focusremains on the application that was in focus on the device, here,application 1.

In FIG. 73, the device 100 with one dual-screen application is docked toa landscape SP in dual-application mode. FIGS. 74 and 75 illustrate thedocking of the device 100 to the SP 1000 in portrait-single applicationmode, where the applications on the device 100, are shown in focus onthe SP 1000.

FIGS. 76-79 illustrate docking to a portrait oriented SP running insingle-application mode. Here, as the device 100 is always open duringdocking, the only “mismatch” can happen when docking to a SP in singleapplication mode. As a general rule of thumb, the application in focusremains visible on the SP. If the SP was last used in single applicationmode, the mode could be remembered upon a re-docking event.

As illustrated more particularly in FIG. 76, application 1 is in focusupon docking to a single-application mode SP, where application 1remains visible and in focus after docking. As shown in sequence 2 inFIG. 77, application 2 is in focus on the device 100 and upon docking tothe single-application mode SP 1000, application 2 remains visible andin focus. Sequence three as illustrated in FIG. 78 illustrates aminimized dual-screen application being in focus when the device 100 isdocked into the SP in single-application mode. Here, the applicationwill be presented in its max mode on the SP 1000 as shown.

Sequence four as illustrated in FIG. 79 shows the situation where amaximized dual-screen application is in view when the device is dockedto the SP in single-application mode. Here, the application will bepresented in max mode on the SP 1000.

FIGS. 80-83 illustrate docking to a landscape oriented SP 1000 runningin single-application mode. Here, if the SP was last used insingle-application mode, the mode could be remembered upon a re-dockingevent as discussed above. As shown in sequence one illustrated in FIG.80, application 1 is in focus upon docking to a single application modeSP, where upon docking, application 1 remains visible after docking. Insequence two illustrated in FIG. 81, application 2 is in focus upondocking to a single-application mode SP, and application 2 remainsvisible after docking.

Sequence 3 as illustrated in FIG. 82 shows a situation where when aminimized dual-screen application is in focus when the handset is dockedto a SP in single-application mode, where the application will bepresented in its max mode on the SP 1000.

Sequence 4 as illustrated in FIG. 83 shows a situation where when amaximized dual-screen application is in view when the device 100 isdocked to the SP 1000 in single-application mode, where the applicationwill be presented in its max mode on the SP 1000.

FIG. 84 illustrates exemplary window management after docking. Ingeneral, and in accordance with an exemplary embodiment, whenapplications are stacked through window management events, a screenshotcan be captured to represent one or more of the applications in thestack. The introduction of the SP 1000 introduces a new level ofcomplexity in handling window management events and applicationscreenshots. In addition to the orientation of the device havingpotentially changed, the device may have also been docked or undocked aswell. This could cause the stacked image to be the wrong size, aspectratio, and/or the like.

As illustrated by step one in FIG. 84, when the application is revealedin the stack and is the wrong size, the application screenshot can bedisplayed as a thumbnail and dimmed. As illustrated by step 1A, to helpthe user to recognize the application, the application icon can beoverlaid on top of the screenshot. Step 2 illustrates than once thescreenshot is completely revealed, the application can be activated.

If the application was suspended at the time, an indicator can informthe user that they may have to wait while the application is activated(re-activated). As illustrated by step 3 in FIG. 84, once theapplication is ready, the application can be displayed at full size andthe dimming effect can be removed. If the application was displayed in adifferent orientation than the corresponding screenshot, the applicationcan also be rotated to its target orientation, if applicable.

The above exemplary steps can occur each time the stored screenshot isnot the same size as the destination area(s) for the application. Theorientation of the screenshot need not be taken into account when makingthis decision, only its size. If the application is the exact size, thecard from the stack can just be introduced in a normal, full size, notdimmed, and no icon arrangement. The corresponding application can thenbe activated and rotated if applicable.

Various situations where mismatched screenshot sizes occur on the SP1000 are discussed below. Note that the orientation of the screenshotconsistently matches the orientation of the SP 1000, not necessarily theorientation of the application. Specifically, in FIG. 85, step 4, ascreenshot from the device (all orientations) on a landscape tabletdual-application SP 1000.

Step 5 in FIG. 85 illustrates a screenshot from landscape tablet singleor portrait tablet single mode on a landscape tablet dual-application SP1000. As illustrated in step 6, an exemplary screenshot is shown for thedevice (all orientations) on a landscape tablet single application SP1000. As illustrated in step 7 in FIG. 85, with a “F” representing agesture, such as a flip or swipe, the SP 1000 is shown with a screenshotfrom a landscape tablet dual or portrait tablet dual on a landscapetablet single SP 1000.

FIG. 86 generally represents an exemplary embodiment of undocking from aportrait oriented SP 1000. When the device 100 is undocked from the SP1000, the device 100 can slide out in a portrait dual-orientation. Uponundocking, the applications should be re-oriented on the device 100accordingly, this being considered a clockwise rotation of the device100.

As shown in sequence one of FIG. 86, the device 100 is undocked from theSP 1000 (in either application mode), and the applications arere-oriented and focus remains on the application that had focus prior toundocking from the SP 1000.

In sequence two in FIG. 86, a maximized dual-screen application remainsmaximized on the SP 1000. Here, standard orientation rules apply.

FIG. 87 illustrates exemplary embodiments of undocking from alandscape-oriented SP 1000. Here, and in accordance with an exemplaryembodiment, when the device 100 is undocked from a landscape-oriented SP1000, the device 100 slides out in a landscape-dual orientation. Uponundocking, the applications should be re-oriented on the handsetaccordingly, with this being considered a clockwise rotation of thedevice 100. As shown in sequence one of FIG. 87, the device 100 isundocked from the SP 1000, in either application mode, and theapplications are re-oriented with focus remaining on the applicationthat had focus prior to the undocking event. As illustrated in sequence2, a maximized dual-screen application remains maximized on the device100. Here, standard orientation rules apply, as does the gravity dropfeature as previously discussed.

FIG. 89 illustrates an exemplary embodiment where the SP is in amulti-application mode. In the multi-application mode, the device 100 isemulated in its mini-tablet form. This mode can be invoked, for example,by engaging the multi-application button, with, in essence, the SP 1000emulating the device 100 being opened.

The multi-application mode can inherit, for example, all of the rulesthat the dual-screen device 100 affords. For instance, all applicationscan be launched in single screen mode. The only notable exception isthat applications that can support max modes can be expanded to thismode, when provided the opportunity.

The multi-application mode can support the following applications:

1. Single screen market place applications.

2. Dual screen internal applications.

Each application can itself determine how it appears in eachorientation. In accordance with one exemplary embodiment, there are someinteraction assumptions that can be made:

Windowing management can navigate full applications.

Windowing management can collapse a dual-screen application into asingle screen view.

The application manager can operate in both orientations, and can allowfor navigation of open applications.

Two sets of menu buttons may be required, and as such can be placed onscreen. This embodiment can use the capacitive button strip to disablethe back and menu buttons, but still support the “home” button.

Personal computer type personality is available via a desktop widget.

As illustrated in FIG. 88, a portrait-tablet, multi-application mode isshown. More particularly, FIG. 88 illustrates one multi-application modeof the SP 1000. Here, the multi-application mode of the SP 1000 emulatesthe device 100 in its mini-tablet form, as discussed, with this modeoptionally being invoked by selection of a multi-application button. Inthis mode, and in accordance with an exemplary embodiment, eachapplication has the ability to determine how the application appears ineach orientation, e.g., portrait and landscape.

FIG. 89 illustrates another exemplary embodiment, where the SP 1000 isin a landscape, multi-application mode. Operation in this embodiment issimilar to that of the SP 1000 in FIG. 88 where the interactionassumptions are comparable, except that the SP 1000 is in landscapetablet, multi-application mode.

FIG. 90 illustrates another exemplary embodiment, where the SP 1000 isin a portrait orientation, multi-application mode. In this exemplaryembodiment, a number of different features are illustrated. First, asnoted by step 1, the multi-application mode is enabled. Through thisenactment, a first application “C” enabled as well as a secondapplication “D” here represented by tasks 2 and 3, respectively. A focusindicator, such as that represented by 2612, feature 4, can further beindicated as previously discussed. Moreover, back, home, and menubuttons, as illustrated by feature 5, can be provided with each of thewindowed applications being individually manageable, manipulatable, andthe like, as previously discussed.

FIG. 91 illustrates an exemplary mode of operation of the SP 1000, in alandscape mode, and further in a multi-application mode. FIG. 91illustrates, with reference to item 1, that the multi-application modehas been enabled. In accordance with this exemplary embodiment, thereare two applications, represented by a first application “D” and asecond application, application “F.” Furthermore, and in accordance withan optional embodiment, focus indicator 2416 (item 4) can be included aswell as the back/home/menu buttons as previously discussed. Again, whilethe focus indicator in FIG. 91 is illustrated as a bar 2416, it shouldbe appreciated that focus can be illustrated in any number of waysincluding one or more of illumination, highlighting, dimming, or ingeneral in any manner which can indicate to the user that, in thisinstance, application “D” is in focus, while application “F” is not infocus.

FIG. 92 illustrates an exemplary method of maximizing/minimizing afull-screen application. As illustrated in FIG. 92, applications thatcan be maximized can expand to either dual screen mode or max mode.Here, application “E1” is expanded to dual screen mode on display 1010.In FIG. 92, and as previously discussed, button 2618 allows the user totoggle between a single screen mode, as previously illustrated, and anemulated dual screen mode, for example, as illustrated in FIGS. 26 and27. Furthermore, and as previously discussed, button 2618 does not haveto include a vertical bar, therefore indicating to the user that the SP1000 is in a single screen mode. Moreover, the focus indicator is nolonger present thereby further providing the user with an indicationthat they are in a single screen mode.

FIG. 93 illustrates an exemplary method for displaying the desktop 2912on display 1010. As in the device 100, when the last application ismoved to the side, via, for example, a gesture or flick type motion, thedesktop can be displayed. In FIG. 93, multi-application mode is enabled,application “F” is shown on display 1010 in conjunction with the desktop2912, and in accordance with this particular embodiment, the desktop isillustrated as being in focus by virtue of the focus indicator 2916.However, as previously discussed, the focus indicator 2916 need notnecessarily be a bar located adjacent desktop display, but could beillustrated, for example, by showing the desktop 2912 with brighterluminance than application “F.”

FIG. 94 illustrates the SP 1000 in a portrait-type orientation, with thekeyboard 9004 being displayed. When the keyboard is required in thisparticular orientation, the application, here displayed in applicationarea 9008, will take over the entire screen, minus the keyboard portion.Moreover, as previously discussed, the keyboard area 9004 can bemanipulated, via either a gesture or stretching or zooming typefunction, to change the size thereof, with the application area 9008being optionally expanded or contracted in unison with the keyboard, asappropriate.

FIG. 95 illustrates an exemplary embodiment of the window stack indual-application mode. In accordance with this exemplary embodiment, thewindowing management acts in a similar manner for the SP 1000 as it doesas previously discussed in relation to the device 100, and the conceptof the windows stack. This same concept of the windows stack describedin relation to the device 100 can be extended and used to explain thebehavior of window management on the SP 1000 when the device is in, forexample, dual mode.

In accordance with one exemplary embodiment, and when the window stackis in a single application mode, the intuitiveness of the two stacks maybe compromised because the user may not necessarily be able to see allrelevant information on the screen. This is similar to what happens whena user closes the device 100 and is only able to see a main, or primaryscreen. Even though the user cannot see the two screens, the two windowstacks don't really disappear, the other stack is still there, but it isoff-screen. Therefore, when a user enacts a window management gestureaway from the buttons (to the right) a user is pushing the activeapplication to the top of the screen stack and revealing the applicationthat is “under” the active one. When a user uses a window managementgesture toward the buttons (to the left) the user is bringing in the top“card’ from the off-screen stack and sliding it on top of the activewindow, effectively covering it, when there is no application left onthe off-screen stack. This is illustrated in FIG. 95. The two-windowstacks are shown as D1 through D6, with the primary, and viewable stack,being illustrated as 1-5 in a grey-shaded color.

Even more specifically, when a gesture is away from the buttons (to theright) and in accordance with this exemplary embodiment, a user pushesthe active application “3” to the top of the off-screen stack, andreveals the application that is under the active one, here application“2.” In a similar manner, when a user gestures towards the buttons (tothe left) the top card (here application 3) is effectively covered byvirtue of card 4 sliding on top of the active window. As previouslydiscussed, this can happen in a linear manner, or can happen in a“rolodex” type of fashion where after application “5” is reached,application 1, which would be “next” in the stack, could be brought intoview on the SP 1000.

Moreover, and as previously discussed, the transition between “cards”can occur in a fluid manner such that as application 3 leaves thescreen, application 4 begins transitioning onto the screen. Inaccordance with an optional exemplary embodiment, and upon detection ofthe appropriate gesture, application 3 can be immediately replaced withapplication 4, application 5, and so on through the sequence, until theend of the stack is reached. The different manners in which applicationsare scrolled through can be based one or more of applicationpreferences, user preferences, or the like. For example, for a gracefultransition one or more of a blend, fade, blur, or comparable effect canbe used, such as to replace application “3” with application “4,” andwith a swap-replace type of action application “3” could be immediatelyreplaced by application “2.” Moreover, a “peak” or preview type ofgesture can be recognized such that as application “3” is transitionedoff of the display 1010, application 2 or 4, depending on the nature ofthe gesture, could be previewed prior to activation. Once the gestureaction is completed the appropriate application could be activated anddisplayed on the display 1010. However, if the gesture action is notcompleted, focus could revert back to application “3” which is indisplay 1010.

FIGS. 96-99 illustrate an exemplary embodiment that addresses themanagement of a “seam” on the SP 1000. In accordance with an exemplaryembodiment, and in order to separate two separate applications from eachother, there can be a visual seam between them. On the device 100, thereis no need for a software scene due to the physical seam separating theapplication views from each other. This of course applies to both theportrait dual and landscape dual orientations of the device 100.However, as illustrated in FIG. 96, the SP 1000 is in a dual-applicationmode, with two separate applications in view, a system-wide seam can bedisplayed in the middle of the screen 1010. The seam 9610 is used to notonly separate the applications, here application 1, which is in focus,and application 2, which is not in focus, but is also used optionally asthe main indication of focus. As illustrated in FIG. 97, the sea canalso be shown when application 2 is in focus with the seam dividing,visually, the two applications for the user.

As illustrated in FIG. 98, when the desktop “D2” is revealed, the seamcan also be shown if only one application is displayed, in conjunctionwith the desktop. As illustrated in FIG. 99, when the desktop isrevealed, or no applications are running, this seam need not bedisplayed. Here, the desktop “D1, D2” is displayed on the SP 1000 withno other applications being present.

The following sequence of figures illustrates toggling between singleand dual application mode on the SP 1000. One unique feature of the SP1000 is to allow switching between single and dual application modes. Inthe following sequence of figures, numerous sequences are displayedillustrating the toggling feature and transitions from a first state toone or more other states. In sequence 1, illustrated in FIGS. 100 and101, the SP 1000 is in a dual-application mode with two single-screenapplications visible. In the sequence in FIG. 100, upon switching to asingle-application mode, the application in focus remains visible. InFIG. 101, however, upon switching back to a dual-application mode, thevisible application is placed in the left-bottom part of the display onthe SP 1000. The SP 1000 can give the user a clear indication of thecurrent application mode “dual or single” through, for example, an iconin the enunciator bar as previously discussed. Switching the SP 1000between single and dual mode is similar in nature to the opening andclosing of the device 100. However, in contrast to the behavior of thedevice 100, the application in focus always remains on screen whenswitching mode. Because of this, if the keyboard is present whenswitching modes, the keyboard can remain visible when the transition iscompleted.

The behavior of dual-screen applications is slightly different and isdescribed with reference to the sequences illustrated in FIGS. 102-104.As illustrated in FIG. 102, dual-screen applications that are notmaximized in dual-application mode go into their max mode when the SP1000 switches to the single application mode, if the applicationsupports it. As illustrated by sequence 2A in FIG. 102, when switchingback, the dual-screen application goes to its non-maximized state.

As illustrated in FIG. 103, dual-screen applications that do not supporta max mode will have one of their views laid-out in single mode when theSP 1000 is switched to a single mode. As illustrated in FIG. 104, atransition is shown where a dual-screen application that is maximized indual-application mode goes to its max mode when the SP 1000 switches tosingle application mode. As illustrated in 4A in FIG. 104, whenswitching back, the dual-screen application goes back to its maximizedstate.

In accordance with this exemplary embodiment, some special transitionsmay be required where the desktop is visible in dual mode on the SP1000. FIG. 105 illustrates that, upon switching to a single-applicationmode, the application in focus (here application 1) remains visible.However, as illustrated in sequence 5A, upon switching back to thedual-application mode, the visible application is placed in theleft-bottom part of the SP 1000 (here application 1).

As illustrated in FIG. 106, if the desktop (D2) happens to have focus,as is illustrated, switching to single-application mode will make thevisible application take over the screen in single mode. As illustratedby sequence 6A in FIG. 106, upon switching back to dual-applicationmode, the visible application is placed on the left-bottom part of thedisplay 1010 on SP 1000 and will keep focus (even if the desktop hadfocus before).

The following exemplary sequence of figures illustrates windowmanagement events in single-application mode on the SP 1000. Morespecifically, window management off-screen gestures insingle-application mode on the SP 1000 behave similarly to a closeddevice 100. As illustrated in FIG. 107, drag and flick type gesturesnavigate between applications in the stack. In this exemplaryembodiment, a drag or flick type gesture transitions from application 1,to application 2, which is in max mode, with a further gesturedisplaying application 3.

As illustrated in FIG. 108, dual-screen applications are presented intheir max mode across the screen, with drag and flick gestures notminimizing or maximizing them. Therefore, a leftward drag or flickgesture in the SP 1000 is focused on application 2 in max mode, wouldtransition to application 3 being displayed.

As illustrated in FIG. 109, drag or flip gesture from FIG. 108 wouldreveal application 3 being displayed on the SP 1000.

As illustrated in FIG. 110, operations or gestures are ignored on the SP1000 as, for example, there are no other applications in the stack. Asillustrated in FIG. 111, rotation events work in a standard manner onthe SP 1000, with max mode orientations rotating to their respectivecounterparts. Gravity drop rules may also apply here if the applicationstructure calls for them. Therefore, in this exemplary embodiment, whenthe SP 1000 transitions from a portrait mode to a landscape mode,application 1 is re-rendered in max mode, landscape orientation.

The following exemplary sequence of figures illustrates an exemplaryembodiment directed toward initiating a preview on the SP 1000. Thedesktop preview action mimics that of the device 100, where applicationsare pushed in the direction of their respective stacks (primary andsecondary). The single application mode corresponds with a closed device100, and a dual application mode corresponds to an open device 100.

In the following sequence of figures, FIG. 112 illustrates an exemplarySP 1000 in a landscape orientation, where, in dual-application mode, theviews on the primary and secondary halves of the screen are pushed inthe direction of the respective stacks, with the SP 1000 rotatedclockwise, primary towards the left, secondary towards the right.

In FIG. 113, and when the SP 1000 is in single application mode, thesingle mode application slides off the screen of the SP 1000 in a singlemotion in the direction of the physical buttons. This reveals thedesktop (D1) as shown in FIG. 113. In FIG. 114, and in dual applicationmode, the views on the primary and secondary halves of the screen on theSP 1000 are pushed in the direction of their respective stacks, e.g.,primary downwards and secondary upwards. In the single application mode,as illustrated in FIG. 115, the single mode application slides off thescreen of the SP 1000 in a single motion in the direction of thephysical buttons, thereby revealing the desktop (D1).

FIGS. 116-119 illustrate the handling of incoming calls on the SP 1000.In accordance with one exemplary embodiment, incoming calls on the SP1000 have an effect on the windows stack, as the incoming call view isconsidered a “new application.” In the following sequence of figures,the handling and displaying of an indication of incoming calls relativeto the window stack is illustrated. More specifically, and in FIG. 116,the SP 1000 is running in dual-application mode, here with twosingle-screen applications in view (1, 2). Upon receipt of an incomingcall, the incoming call is launched on the primary screen, replacing theapplication in that view in accordance with standard application launchrules, user preferences, application priorities, and/or the like.

In FIG. 117, the SP 1000 is running in dual-application mode, with amaximized dual-screen application in view. Here, the incoming call islaunched on the primary screen, with the dual-screen application beingminimized to the opposite screen again in accordance with standardapplication launch rules, user preferences, or the like. In FIG. 118,the SP 1000 is running in single-application mode, with a single-screenapplication in view. First, the incoming call switches the SP 1000 tothe dual-application mode. This has an effect on the application, but inthis particular case, the standard application launching rules areignored in the application that was in view prior to the call will bemoved to the secondary part of the screen, instead of being pushed outof view.

In FIG. 119, the SP 1000 is running in single-application mode, with asingle-screen application in view. First, the incoming call switches theSP 1000 to the dual-application mode. This has an effect on theapplication, and the application is then minimized. The incoming callapplication is launched on the primary side of the SP 1000.

FIG. 120 illustrates an exemplary method of displaying applicationnotifications on the SP 1000. As generally discussed above, and whetherin the portrait or landscape mode, notifications and status/togglebuttons can be provided on the SP 1000 to allow the user to, forexample, toggle on or off Bluetooth, Wi-Fi, screen locking, dual orsingle screen mode, power options, and the like. These, as well as otheroptions, are generally shown in area 1202. In accordance with thisexemplary embodiment, the notifications in the SP 1000 have a behaviorsimilar or identical to that of device 100 in single-screen mode. Here,setting widgets are available via the notifications bar with a settingof widgets including, for example, standard setting widgets such asWi-Fi toggle, Bluetooth, and the like, the screen lock toggle, wherethis will lock the screen, and not allow it to rotate, where a lockindicator can optionally be provided in the annunciator bar, asingle-dual application toggle, where there can be three states totoggle through, dual application mode, single application mode, andsingle application lock, and a power toggle mode that includes, togglingbetween device optimized, smartpad optimized or user preference.

As illustrated in FIGS. 120 and 121, the notifications drawer isillustrated in a similar manner whether the SP 1000 is in tablet mode,as illustrated in FIG. 120, or landscape mode, as illustrated in FIG.121 with the notifications drawer 1202 containing similar features.

As illustrated in FIG. 122, one or more specific hardware interactionson the SP 1000 can trigger a notification. For example, one or more ofthe following hardware interactions can trigger a notification, that canbe one or more of audible and visual: Pressing of the power button,inserting a headphone jack, inserting or removing of a power adapter,inserting or removing of a memory card, such as an SD card, and pressingof any of the buttons on the device 100, such as the mute button, volumebuttons, or the like. As illustrated in FIG. 122, pressing of, forexample, the mute button on the device 100 will also activate the mutingfunction on the SP 1000. Similarly, the pressing of the up/down volumebutton on the device 100 triggers a corresponding up or down volumechange on the SP 1000. As will be appreciated, and with theactivation/deactivation or manipulation of any of the above-mentionedhardware capabilities of the SP 1000 or device 100 one or more ofaudible, visual, or tactile feedback can be provided to the userindicating the corresponding activation/deactivation as appropriate.

FIG. 123 illustrates an exemplary embodiment of a device 100 docked withthe SP 1000, and interactions between the respective batteries on eachdevice, and corresponding battery measurement modules. In accordancewith the exemplary embodiment, each device has its own respectivebattery measurement module (1234, 1238). It should be appreciatedhowever that battery management can be governed by one or more of thebattery measurement modules, with each battery measurement modulerespectively able to control the charging/discharging of battery in theSP 1000 and/or the battery in the device 100. In accordance with oneexemplary embodiment, the SP 1000 has a setting that allows rechargingof the device 100's battery using the SP's power. This can be a defaultbehavior when the SP is plugged into AC power. However, when the SP isnot plugged in, and as in, for example, an extended pad experience mode,the SP 1000 can automatically manage whether or not it will send powerto the device 100. The algorithm to accomplish this can be as follows:

To turn device charging on, if the device charges less than 60% anddevice charge is less than SP charge, send charge to the device, orelse, do nothing. Then, for turning charging off, if the device chargesgreater than 65% or the device charges greater than and equal to the SPcharge plus some percentage, such as 5%, turn off the device charging,otherwise do nothing.

This is illustrated in more detail in FIG. 124. In particular, controlbegins in step S1244. In step S1248 the handset, or device, charging isturned on. Next, in step S12412, a determination is made as to whetherthe handset charge is less than 60% and the handset charge is less thanthe SP charge. If so, control continues to step S1214 where power issent to the handset with control jumping back to step A. Otherwise,control continues to step S12416 where nothing is done, with controlcontinuing to step S12420 where the control sequence ends.

However, if handset charging is to be turned off, control continues tostep S12424. Next, in step S12428, a determination is made whether thehandset charge is greater than 65% or the handset charge is greater thanor equal to the SP charge plus 5%. If so, control continues to stepS12436 where handset charging is turned off, with control continuing tostep S12440 where the control sequence ends.

Otherwise, control continues to step S12432 where nothing is done withcontrol continuing to step S12440 where the control sequence ends.

While the above exemplary embodiment has been described in relation tocertain percentages of charge of one or more of the device 100 and SP1000, it should be appreciated that these percentages can be based onone or more of manufacturer specifications, user specifications, orpreferences, or the like. They are not limited to the specificembodiment illustrated herein. In general, any percentage value can beused with success, provided the device supplying charge has more powerthan the device receiving charge.

FIG. 125 outlines an exemplary method of managing one or more windowswith suspended applications. Suspended applications can use a screencapture of the application to assist with the visual affordance fornavigating the application stack. Between the device 100 and SP 1000,many suspended and oriented application screen captures can exist.Although the screen captures can occur throughout all modes, for thepurpose of simplifying the screen capture sizes, the following exemplaryembodiment only outlines the individual dimensions to make up themajority of sizes across modes.

In other words, since the dimensions are capable of being flippedbetween width and height, the rectangular shape of the screen captureremains the same. When using window management to navigate theapplication stack, the screen captures are revealed. Due to the variousscreen capture irregular sizes, the screen capture that is suspendedentering the active area should follow the following rules: (1)Optionally rotate to match the aspect ratio (wide versus tall), (2)scale direction should be dependent on the device to avoid black bars(pick the shortest dimension), (3) Crop/clip the areas that exceed theaspect ratio requirement, (4) Apply the suspended application screencapture treatment. As discussed hereinafter, various rules and exemplarymanagement operations are discussed relating to the handling ofsuspended applications, and window management.

As illustrated in FIG. 125, device 100 can be in a plurality ofdifferent orientations, portrait single, landscape single, portraitdual, and landscape dual, and the SP-1000 can similarly be a number ofdifferent orientations, such as portrait tablet single application mode,landscape tablet single application mode, landscape tablet dualapplication mode, and portrait tablet dual application mode. Asillustrated in FIG. 125, transitioning between a docked and undockedstate may require the management of the windows from the device 100 tothe SP 1000, or vice versa.

As illustrated in FIG. 126, an exemplary overview of irregular sizeapplications and corresponding screen capture displays is shown. In thisexemplary chart, an outline of the window management screenshot sizes isshown which is derived from the device 100 and the SP 1000 orientationsand the final display size that can be used. The chart is shown with theoriginal screen capture in the left hand column, and the scaled screencapture orientation size and clipping mask in the rows to the right. Inthis exemplary chart, six different resolutions are shown, 480×800,800×480, 640×800, 800×640, 1280×800, and 800×1280.

As illustrated in FIG. 127, to lessen the differences in screen sizesand orientations, some graphical affordance has been created to uniteand normalize differences between the screen capture content, sizes, andunfamiliar orientations. More specifically, vignetting is illustrated byitem 1 in FIG. 127, screen glare is illustrated by item 2 in FIG. 127,an application label is illustrated by item 3 in FIG. 127, havingeither, for example, a horizontal alignment in the center or a verticalalignment in the center, and application text is illustrated by item 4in FIG. 127 including attributes such as font, color, horizontalalignment, and vertical alignment. The combination of one or more of theabove features can be used to harmonize and lessen the differences inscreen sizes and orientations.

As illustrated in FIG. 128, composited application screen captures areshown in accordance with one exemplary embodiment. Here, for everyscreen capture being revealed via the window management, the vignettedesign and label can be applied over the screen capture. Here, withreference to frame 1 in FIG. 128, a device 100 screen capture example isprovided in portrait single mode. In capture 2, an SP 1000 screencapture example is provided in landscape tablet dual mode. For item 3, acomposited application screen capture is shown that can be used inaccordance with an exemplary embodiment.

In FIG. 129, an exemplary embodiment of suspended application screencapture designs are shown. Frame 1 in FIG. 129 shows a SP 1000 capture,with the SP 1000 running in landscape tablet dual mode. In frame 2, theexample illustrates a suspended application being brought into thedevice 100. The application was captured from the SP 1000 in landscapetablet dual mode. With the device 100 being in portrait dual mode, thesuspended application can be presented as shown, to then be revealed andawakened.

In frame 3 of FIG. 129, an example is shown of the application havingbeen refreshed and active.

FIG. 130 illustrates suspended applications moving onto the device 100.Here, and in sequence 1, device 100 screen captures are shown revealingwithin the display 1010. During this orientation, the device 100captures do not require to be resized or trimmed. This is due to thescreen capture being horizontally and vertically equal in both width andheight of the live screen.

As illustrated in sequence 2, SP 1000 screen captures are shownrevealing within the device 100 display. Due to the SP 1000 screencapture sizes, a percentage in scale may occur followed by cropping ofthe image for portions that, for example, bleed outside the desiredactive screen area. In sequence 3, the SP 1000 in single applicationmode screen capture is shown being revealed within the device 100 screenor display. As shown in captures 2 and 3, there are clipped and scaledareas, respectively, corresponding to how the screen capture will bemanaged after the transition to the device 100. In sequence 2, the righthand side of the image is arbitrarily clipped to allow undistortedrendering on the device 100. In sequence 3, the green box illustrates anexemplary scaling procedure that is again utilized for appropriateresizing of the image on device 100.

FIG. 131 illustrates two additional sequences showing exemplary methodsfor suspended applications being moved onto the SP 1000. In sequence 1,the device 100 screen capture is shown revealing within the SP 1000display. In sequence 2, the SP 1000 screen capture is shown revealingwithin the SP 1000 display. Again, scaling and clipping are shown in thesuspended screen capture sequences with, on the left hand side of FIG.131 showing the screens within the suspended applications.

As will be appreciated, while FIG. 130 shows the scaling and clippingoperations occurring independently of one another, as shown in FIG. 131,the scaling and clipping operations can be performed on the same screen,to again assist with display and rendering from the device beingtransitioned to.

FIG. 132 outlines an exemplary method for handling and managing chargingof one or more of the device and smartpad. In particular, control startsin step S1324 and continues to step S1328. In step S1328, adetermination is made as to whether the device is docked. If the deviceis docked, control jumps to step S13228, with control otherwise continueto step S13212. In step S13212, a determination is made as to whetherthe smartpad is charging. If the smartpad is charging, control continuesto step S13224, with control otherwise continuing to step S13216. Instep S13224, one or more of a dock message, battery level indicator, andbattery charging indicator can be displayed with control continuing tostep S13220 where the control sequence ends.

In step S13216, one or more of a dock message and battery levelindicator can be displayed, with control continuing to step S13220.

In step S13228, a determination is made as to whether the device ischarged. If the device is charged, control jumps to step S13212 withcontrol otherwise continuing to step S13232. In step S13232, adetermination is made as to whether the smartpad is charging. If thesmartpad is not charging, control jumps to step S13240. Otherwise,control continues to step S13236. In step S13236, one or more of a deaddevice message, a battery level indicator on the onscreen display and acharging indicator on the onscreen display is shown, with controlcontinuing to step S13220 where the control sequence ends.

In step S13240, one or more of a dead device message is displayed and abattery level indicator message is displayed with control continuing tostep S13220 where the control sequence ends.

FIG. 133 illustrates an exemplary method for managing one or more of thekeyboard and slider bar. In particular, control begins in step SK4 andcontinues to step SK8. In step SK8, a default keyboard can be displayed.As discussed, this default keyboard can be dynamically based, forexample, on one or more of user preferences and current application infocus. In a similar manner, in step SK12, a default slider bar can bechosen based on one or more of user preferences and the applicationcurrently in focus. As generally discussed, both the keyboard and sliderbar can be designed to include characters that are most commonly usedfor the application in focus. Control than continues to step SK16.

In step SK16, a determination is made if a request for a differentkeyboard has been detected. If a request for a different keyboard hasbeen detected, for example, based on a user request or based on anapplication coming into focus, control continues to step SK20 withcontrol otherwise continuing to step SK24. In step SK20, the display onthe device or the smartpad is updated with the requested keyboard.Control than continues to step SK24.

In step SK24, a determination is made whether a request for a differentslider bar has been detected. If a request for a different slider barhas been detected, for example based on a new application coming intofocus and/or user input, control continues to step SK32 where thedisplay is updated on either the device or the smartpad with therequested slider bar. An optional embodiment also updates the slider barindicator for illustrating to the user which slider bar is currentlyselected and active. Control then continues to step SK28 where thecontrol sequence ends.

FIG. 134 illustrates an exemplary embodiment of window management. Inparticular, control begins in step SF4 and continues to step SF8. Instep SF8, the device is docked that is running two single-screenapplications. Upon docking, to a portrait tablet in dual applicationmode, focus is maintained on the application on the SP that was in focuson the device. (See SF8-SF12). Controlling continues to step SF16 wherethe control sequence ends.

FIG. 135 illustrates an exemplary method for window management when adevice with one dual-screen application is docked to a portrait tabletSP in dual-application mode. Here, control begins in step SG4 andcontinues to step SG8. In step SG8, the device with the one dual-screenapplication is docked to the SP running in dual-application mode. Instep SG12 gravity drop is applied to render the dual screen applicationon the SP. Control than continues to step SG16 where the controlsequence ends.

FIG. 136 outlines an exemplary method for window management duringdocking for a handset with two single-screen applications being dockedto a landscape tablet in dual-application mode. Here, control begins instep SH4 and continues to step SH8. In step SH8, a device with twosingle-screen applications is docked to a landscaped tablet indual-application mode. In step SH12, focus on the SP is maintained withthe application that was in focus with the device. Control thancontinues to step SH16 where the control sequence ends.

FIG. 137 illustrates an exemplary method of docking a device with onedual-screen application to a landscape tablet in dual-application mode.Control begins in step SI4 and continues to step SI8. In step SI8, adevice with one dual-screen application is docked to a landscape tabletin dual application mode. Next, in step SI12, both screens of the dualscreen application from the device are displayed on the SP with controlcontinuing to step SI16.

FIG. 138 illustrates an exemplary method for window management duringdocking of a minimized dual screen application on the device with a SPin single-application made. Control begins in step SJ4 and continues tostep SJ8. In step SJ8, a device with a minimized dual screen applicationis docked to a SP in single application mode. In step SJ12, theapplication is displayed in max mode on the SP. Control than continuesto step SJ16 where the control sequence ends.

FIG. 139 illustrates a method for docking a maximized dual-screen devicewith a SP in single-application mode. Control begins in step SK4 andcontinues to step SK8. In step SK8, a device with a maximizeddual-screen application is docked to an SP in single application mode.In step SK12, the application is displayed in max mode on the SP withcontrol continuing to step SK16 where the control sequence ends.

While all of the above described methodologies are in relation todocking to an SP in portrait mode, comparable methodologies are usedwhen docking to an SP in landscape mode.

FIG. 140 outlines an exemplary method for providing feedback to a userbased on a changed hardware state. In particular, control begins withstep SL4 and continues to step SL8. In step SL8, pressing of a hardwarebutton and/or the engagement or disengagement of hardware on the deviceand/or the SP is detected. For example, these could include pressing ofa mute button, the insertion of a head phone jack, the removal of a headphone jack, the insertion of an SD card in the card slot, or the like.Then, in step SL12, one or more of audible, visual, and tactile feedbackare provided to the user indicating that the change in hardware statehas been detected. As discussed, user can optionally be providedinformation regarding which hardware change has been detected withfeedback provided to the user indicating, for example, an SD card hasbeen inserted. Control then continues to step SL16 where the controlsequence ends.

The exemplary systems and methods of this disclosure have been describedin relation to a smartpad (SP) and a device, and interactiontherebetween. However, to avoid unnecessarily obscuring the presentdisclosure, the preceding description omits a number of known structuresand devices. This omission is not to be construed as a limitation of thescopes of the claims. Specific details are set forth to provide anunderstanding of the present disclosure. It should however beappreciated that the present disclosure may be practiced in a variety ofways beyond the specific detail set forth herein.

For example, the smartpad could have multiple physical and/or logicalscreens/displays. Additionally, the smartpad could be used with one ormore input devices such as a stylus, mouse, or the like. Moreover, thesmartpad could be populated with a processor, memory, communicationsmeans and the like that would allow for stand-alone operation. Evenfurther, the smartpad could be associated or docked with other types ofcommunications devices such as a smartphone such that the smartpad couldbe used as a display and/or I/O interface therefore.

Furthermore, while the exemplary aspects, embodiments, and/orconfigurations illustrated herein show the various components of thesystem collocated, certain components of the system can be locatedremotely, at distant portions of a distributed network, such as a LANand/or the Internet, or within a dedicated system. Thus, it should beappreciated, that the components of the system can be combined in to oneor more devices, such as a tablet-like device, or collocated on aparticular node of a distributed network, such as an analog and/ordigital telecommunications network, a packet-switch network, or acircuit-switched network. It will be appreciated from the precedingdescription, and for reasons of computational efficiency, that thecomponents of the system can be arranged at any location within adistributed network of components without affecting the operation of thesystem. For example, the various components can be located in a switchsuch as a PBX and media server, gateway, in one or more communicationsdevices, at one or more users' premises, or some combination thereof.Similarly, one or more functional portions of the system could bedistributed between a telecommunications device(s) and an associatedcomputing device.

Furthermore, it should be appreciated that the various links connectingthe elements can be wired or wireless links, or any combination thereof,or any other known or later developed element(s) that is capable ofsupplying and/or communicating data to and from the connected elements.These wired or wireless links can also be secure links and may becapable of communicating encrypted information. Transmission media usedas links, for example, can be any suitable carrier for electricalsignals, including coaxial cables, copper wire and fiber optics, and maytake the form of acoustic or light waves, such as those generated duringradio-wave and infra-red data communications.

Also, while the flowcharts have been discussed and illustrated inrelation to a particular sequence of events, it should be appreciatedthat changes, additions, and omissions to this sequence can occurwithout materially affecting the operation of the disclosed embodiments,configuration, and aspects.

In yet another embodiment, the systems and methods of this disclosurecan be implemented in conjunction with a special purpose computer, aprogrammed microprocessor or microcontroller and peripheral integratedcircuit element(s), an ASIC or other integrated circuit, a digitalsignal processor, a hard-wired electronic or logic circuit such asdiscrete element circuit, a programmable logic device or gate array suchas PLD, PLA, FPGA, PAL, special purpose computer, any comparable means,or the like. In general, any device(s) or means capable of implementingthe methodology illustrated herein can be used to implement the variousaspects of this disclosure. Exemplary hardware that can be used for thedisclosed embodiments, configurations and aspects includes computers,handheld devices, telephones (e.g., cellular, Internet enabled, digital,analog, hybrids, and others), and other hardware known in the art. Someof these devices include processors (e.g., a single or multiplemicroprocessors), memory, nonvolatile storage, input devices, and outputdevices. Furthermore, alternative software implementations including,but not limited to, distributed processing or component/objectdistributed processing, parallel processing, or virtual machineprocessing can also be constructed to implement the methods describedherein.

In yet another embodiment, the disclosed methods may be readilyimplemented in conjunction with software using object or object-orientedsoftware development environments that provide portable source code thatcan be used on a variety of computer or workstation platforms.Alternatively, the disclosed system may be implemented partially orfully in hardware using standard logic circuits or VLSI design. Whethersoftware or hardware is used to implement the systems in accordance withthis disclosure is dependent on the speed and/or efficiency requirementsof the system, the particular function, and the particular software orhardware systems or microprocessor or microcomputer systems beingutilized.

In yet another embodiment, the disclosed methods may be partiallyimplemented in software that can be stored on a storage medium, executedon programmed general-purpose computer with the cooperation of acontroller and memory, a special purpose computer, a microprocessor, orthe like. In these instances, the systems and methods of this disclosurecan be implemented as program embedded on personal computer such as anapplet, JAVA® or CGI script, as a resource residing on a server orcomputer workstation, as a routine embedded in a dedicated measurementsystem, system component, or the like. The system can also beimplemented by physically incorporating the system and/or method into asoftware and/or hardware system.

Although the present disclosure describes components and functionsimplemented in the aspects, embodiments, and/or configurations withreference to particular standards and protocols, the aspects,embodiments, and/or configurations are not limited to such standards andprotocols. Other similar standards and protocols not mentioned hereinare in existence and are considered to be included in the presentdisclosure. Moreover, the standards and protocols mentioned herein andother similar standards and protocols not mentioned herein areperiodically superseded by faster or more effective equivalents havingessentially the same functions. Such replacement standards and protocolshaving the same functions are considered equivalents included in thepresent disclosure.

The present disclosure, in various aspects, embodiments, and/orconfigurations, includes components, methods, processes, systems and/orapparatus substantially as depicted and described herein, includingvarious aspects, embodiments, configurations embodiments,subcombinations, and/or subsets thereof. Those of skill in the art willunderstand how to make and use the disclosed aspects, embodiments,and/or configurations after understanding the present disclosure. Thepresent disclosure, in various aspects, embodiments, and/orconfigurations, includes providing devices and processes in the absenceof items not depicted and/or described herein or in various aspects,embodiments, and/or configurations hereof, including in the absence ofsuch items as may have been used in previous devices or processes, e.g.,for improving performance, achieving ease and\or reducing cost ofimplementation.

The foregoing discussion has been presented for purposes of illustrationand description. The foregoing is not intended to limit the disclosureto the form or forms disclosed herein. In the foregoing DetailedDescription for example, various features of the disclosure are groupedtogether in one or more aspects, embodiments, and/or configurations forthe purpose of streamlining the disclosure. The features of the aspects,embodiments, and/or configurations of the disclosure may be combined inalternate aspects, embodiments, and/or configurations other than thosediscussed above. This method of disclosure is not to be interpreted asreflecting an intention that the claims require more features than areexpressly recited in each claim. Rather, as the following claimsreflect, inventive aspects lie in less than all features of a singleforegoing disclosed aspect, embodiment, and/or configuration. Thus, thefollowing claims are hereby incorporated into this Detailed Description,with each claim standing on its own as a separate preferred embodimentof the disclosure.

Moreover, though the description has included description of one or moreaspects, embodiments, and/or configurations and certain variations andmodifications, other variations, combinations, and modifications arewithin the scope of the disclosure, e.g., as may be within the skill andknowledge of those in the art, after understanding the presentdisclosure. It is intended to obtain rights which include alternativeaspects, embodiments, and/or configurations to the extent permitted,including alternate, interchangeable and/or equivalent structures,functions, ranges or steps to those claimed, whether or not suchalternate, interchangeable and/or equivalent structures, functions,ranges or steps are disclosed herein, and without intending to publiclydedicate any patentable subject matter.

What is claimed is:
 1. A smartpad comprising: a display; an interface adapted to receive a dual touch screen device, wherein content from the dual touch screen device is displayable on the display of the smartpad; middleware implemented as a multi-display management class on the dual touch screen device that includes one or more modules adapted to manage the display of the content from the dual touch screen device on the display of the smartpad; and a capacitive button on the smartpad that toggles between one or more application modes on the smartpad for at least one application running on the dual screen device, the one or more application modes including a single application mode and a multiple application mode, the single application mode showing one application fully on the display, the multiple application mode emulating on the display the dual touch screens of the dual touch screen device when the dual touch screen device is in an open state.
 2. The smartpad of claim 1, further comprising a gesture capture region.
 3. The smartpad of claim 1, further comprising one or more of a headphone jack, a power button, at least one camera, a power connector and one or more configurable areas.
 4. The smartpad of claim 1, further comprising one or more of a wired and wireless communications link between the dual touch screen device and the smartpad.
 5. The smartpad of claim 1, further comprising a window management module adapted to transition information displayed on the dual touch screen device to the display on the smartpad.
 6. The smartpad of claim 1, wherein the dual touch screen device docks to a receiving port in the smartpad.
 7. The smartpad of claim 1, further comprising one or more of a line in jack, a line out jack, a microphone jack and a communication port.
 8. The smartpad of claim 1, wherein the display is capable of rendering the content displayed on each of the screens on the dual touch screen device upon docking of the dual touch screen device to the smartpad.
 9. The smartpad of claim 1, further comprising: a link between the smartpad and the dual touch screen device allowing the exchange of power; and a link between the smartpad and a dock adapted for charging the smartpad, wherein the dock can further be used to charge the dual screen device, the dock including one or more of a headphone jack, a line jack, a USB connector, an AC port and a display port, all connectable to one or more of the smartpad and the dual screen device.
 10. The smartpad of claim 1, wherein the display is a touch sensitive display.
 11. A method for operating a smartpad comprising: receiving a dual screen device in an interface, wherein content from the dual touch screen device is displayable on a touch screen display of the smartpad when a docking event is detected; managing the display of the content from the dual touch screen device on the display of the smartpad by middleware implemented as a multi-display management class on the dual touch screen device; and toggling between one or more application modes, for at least one application running on the dual touch screen device, on the smartpad based on an input received from a capacitive button on the smartpad, the one or more application modes including a single application mode and a multiple application mode, the single application mode showing one application fully on the display, the multiple application mode emulating on the display the dual touch screens of the dual touch screen device when the dual touch screen device is in an open state.
 12. The method of claim 11, further comprising detecting one or more gestures in a gesture capture region.
 13. The method of claim 11, wherein the smartpad includes one or more of a headphone jack, a power button, at least one camera, a power connector and one or more configurable areas.
 14. The method of claim 11, wherein the smartpad includes one or more of a wired and wireless communications link between the dual touch screen device and the smartpad.
 15. The method of claim 11, further comprising transitioning information displayed on the dual touch screen device to the display on the smartpad.
 16. The method of claim 11, wherein the dual screen device docks to a receiving port in the smartpad.
 17. The method of claim 11, wherein the smartpad includes one or more of a line in jack, a line out jack, a microphone jack and a communication port.
 18. The method of claim 11, wherein the display is capable of rendering the content displayed on each of the screens on the dual touch screen device upon docking of the dual touch screen device to the smartpad.
 19. The method of claim 11, further comprising exchanging power on a link between the smartpad and the dual screen device.
 20. The method of claim 11, wherein the display is a touch sensitive display. 